View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004365 | SymmetricDS Pro | Bug | public | 2020-04-24 16:26 | 2020-04-24 16:26 |
| Reporter | pmarzullo | Assigned To | |||
| Priority | normal | ||||
| Status | new | Resolution | open | ||
| Product Version | 3.11.8 | ||||
| Summary | 0004365: Initial load request grabs list of active trigger histories too soon | ||||
| Description | When a new node is created, and sync triggers is being run for that node, you can ask for an initial load for that node before the triggers are done being synchronized. The initial load request can be picked up and the active trigger histories list is queried for (while the triggers are being synchronized). When the initial load request is then processed, it asks for a synch triggers lock, and if the synch triggers is being run, then it will wait until it is complete. But the damage of missing tables is already done. The list of active trigger histories should be queried for after getting the synch triggers lock so that the list is complete. | ||||
| Steps To Reproduce | 1. Create a new node with a bunch of tables that can be synchronized. 2. Synch triggers for this node. 3. Immediately request an initial load request (before the synch triggers is complete). 4. Not all tables will be requested to initial load. | ||||
| Tags | initial/partial load | ||||