View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006091 | SymmetricDS | Bug | public | 2023-11-03 18:56 | 2023-11-15 18:20 |
| Reporter | jkeyne | Assigned To | |||
| Priority | normal | ||||
| Status | closed | Resolution | no change required | ||
| Product Version | 3.15.0 | ||||
| Summary | 0006091: Sometimes when registering nodes, another node loses its registration | ||||
| Description | While registering more than 3 nodes, occasionally one or more nodes will lose their registration. The logs seem to say that while another node is being registered, a foreign key violation is detected on `sym_node`. In an attempt to resolve it, the node deletes a row from `sym_node_security`, however the row it ends up deleting is its own row, thus removing its own password and causing the node to unregister itself. I originally noticed this while running symmetrcids 3.14.3, but I upgraded to 3.15.0 and was still able to replicate the issue. I've tried re-registering the node, but usually that causes a different node to lose its registration afterwards. I'm attaching logs with debugging enabled. The logs show an attempt at registering 5 nodes. Shortly after registering the 5th node (m-site5) at 2023-10-30 17:41:30,984, the 2nd node (m-site2) experiences the issue beginning at 2023-10-30 17:42:22,452. Also, here's a table briefly describing each node: | Server name | node id | group id | engine id | log path | | ---------------------------------------- | ------- | --------- | ----------- | ------------------- | | Site1 (master node) | m-site1 | g-m-site1 | eng-m-site1 | Site1/symmetric.log | | Site2 (the node that loses registration) | m-site2 | g-m-site2 | eng-m-site2 | Site2/symmetric.log | | Site3 | m-site3 | g-m-site3 | eng-m-site3 | Site3/symmetric.log | | Site4 | m-site4 | g-m-site4 | eng-m-site4 | Site4/symmetric.log | | Site5 | m-site5 | g-m-site5 | eng-m-site5 | Site5/symmetric.log | | ||||
| Tags | No tags attached. | ||||
|
|
|
|
|
Does the issue still occur if you set the following parameter to false and disable sync_on_incoming on your triggers? auto.sync.configuration.on.incoming=false |
|
|
Setting that parameter seems to fix it. Just did a quick test where I was able to add 8 servers successfully. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-11-03 18:56 | jkeyne | New Issue | |
| 2023-11-03 18:56 | jkeyne | File Added: Debuglogs.zip | |
| 2023-11-08 18:57 | emiller | Status | new => feedback |
| 2023-11-08 18:57 | emiller | Note Added: 0002395 | |
| 2023-11-08 20:42 | jkeyne | Note Added: 0002396 | |
| 2023-11-08 20:42 | jkeyne | Status | feedback => new |
| 2023-11-15 18:20 | cquamme | Status | new => closed |
| 2023-11-15 18:20 | cquamme | Resolution | open => no change required |