View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0005510SymmetricDSBugpublic2022-10-04 20:192022-11-30 19:49
Reporterelong Assigned Toelong  
Prioritynormal 
Status closedResolutionfixed 
Product Version3.8.12 
Target Version3.14.3Fixed in Version3.14.3 
Summary0005510: Multiple active trigger history for same table
DescriptionWhen 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 Reproduce1. stop routing
2. run heartbeat job
3. delete from sym_trigger_hist
4. restart
Tagstrigger

Relationships

related to 0005509 closedelong Multiple active trigger history for same table 
related to 0002944 closedchenson Attempt to recover if sym_trigger_hist is deleted. If the table and trigger can be found then recreate the row. 

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2022-10-04 20:19 elong New Issue
2022-10-04 20:19 elong Status new => assigned
2022-10-04 20:19 elong Assigned To => elong
2022-10-04 20:19 elong Tag Attached: trigger
2022-10-04 20:19 elong Issue generated from: 0005509
2022-10-04 20:19 elong Relationship added related to 0005509
2022-10-04 20:19 elong Relationship added related to 0002944
2022-10-04 20:21 elong Status assigned => resolved
2022-10-04 20:21 elong Resolution open => fixed
2022-10-04 20:21 elong Fixed in Version => 3.14.3
2022-11-30 19:49 admin Status resolved => closed