View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005508 | SymmetricDS | Bug | public | 2022-10-04 19:53 | 2022-11-30 19:34 |
| Reporter | elong | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.8.12 | ||||
| Target Version | 3.12.20 | Fixed in Version | 3.12.20 | ||
| Summary | 0005508: Multiple active trigger history for same table | ||||
| Description | When routing encounters a trigger hist ID that does not exist, it creates a new trigger history for it, even if there is a newer, existing trigger history (for the same trigger, table, catalog, and schema). 2022-10-04 14:00:54,155 WARN [server] [DataService] [server-router-reader-1] Could not find a trigger history row for the table sym_node for data_id 272. Generating a new trigger history row. Multiple active trigger histories can create problems for replication, such as sending a table multiple times during the initial load. | ||||
| Steps To Reproduce | 1. stop routing 2. run heartbeat job 3. delete from sym_trigger_hist 4. restart | ||||
| Tags | trigger | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-10-04 19:53 | elong | New Issue | |
| 2022-10-04 19:53 | elong | Status | new => assigned |
| 2022-10-04 19:53 | elong | Assigned To | => elong |
| 2022-10-04 19:53 | elong | Tag Attached: trigger | |
| 2022-10-04 19:54 | elong | Relationship added | related to 0002944 |
| 2022-10-04 20:00 | admin | Changeset attached | => SymmetricDS 3.12 ff240432 |
| 2022-10-04 20:00 | elong | Status | assigned => resolved |
| 2022-10-04 20:00 | elong | Resolution | open => fixed |
| 2022-10-04 20:00 | elong | Fixed in Version | => 3.12.20 |
| 2022-10-04 20:02 | elong | Issue cloned: 0005509 | |
| 2022-10-04 20:02 | elong | Relationship added | related to 0005509 |
| 2022-11-30 19:34 | admin | Status | resolved => closed |