View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005509 | SymmetricDS | Bug | public | 2022-10-04 20:02 | 2022-11-30 19:40 |
| Reporter | elong | Assigned To | elong | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.8.12 | ||||
| Target Version | 3.13.9 | Fixed in Version | 3.13.9 | ||
| Summary | 0005509: 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 | ||||
| related to | 0005508 | closed | elong | Multiple active trigger history for same table |
| related to | 0002944 | closed | chenson | Attempt to recover if sym_trigger_hist is deleted. If the table and trigger can be found then recreate the row. |
| related to | 0005510 | closed | elong | Multiple active trigger history for same table |
|
SymmetricDS: 3.13 09c988e2 2022-10-04 20:18:33 Details Diff |
0005509: Multiple active trigger history for same table |
Affected Issues 0005509 |
|
| mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/DataService.java | Diff File | ||
|
SymmetricDS: 3.14 0403cd63 2022-10-04 20:18:33 Details Diff |
0005509: Multiple active trigger history for same table |
Affected Issues 0005509 |
|
| mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/DataService.java | Diff File | ||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-10-04 20:02 | elong | New Issue | |
| 2022-10-04 20:02 | elong | Status | new => assigned |
| 2022-10-04 20:02 | elong | Assigned To | => elong |
| 2022-10-04 20:02 | elong | Tag Attached: trigger | |
| 2022-10-04 20:02 | elong | Issue generated from: 0005508 | |
| 2022-10-04 20:02 | elong | Relationship added | related to 0005508 |
| 2022-10-04 20:02 | elong | Relationship added | related to 0002944 |
| 2022-10-04 20:18 | elong | Status | assigned => resolved |
| 2022-10-04 20:18 | elong | Resolution | open => fixed |
| 2022-10-04 20:18 | elong | Fixed in Version | => 3.13.9 |
| 2022-10-04 20:19 | elong | Issue cloned: 0005510 | |
| 2022-10-04 20:19 | elong | Relationship added | related to 0005510 |
| 2022-10-04 21:00 | admin | Changeset attached | => SymmetricDS 3.13 09c988e2 |
| 2022-10-04 21:00 | admin | Changeset attached | => SymmetricDS 3.14 0403cd63 |
| 2022-11-30 19:40 | admin | Status | resolved => closed |