View Issue Details

IDProjectCategoryView StatusLast Update
0004204SymmetricDSImprovementpublic2020-01-02 09:42
ReporterelongAssigned Toelong 
Prioritynormal 
Status closedResolutionfixed 
Product Version3.11.0 
Target Version3.11.3Fixed in Version3.11.3 
Summary0004204: Efficient logging of trigger hist and trigger router problems
DescriptionThe Router Service and Data Extractor Service handle problems with trigger history and trigger routers, which are logged for every row. The logging can slow the system down. It also flushes the cache each time, further slowing down the system. Instead, log each unique type of problem and give an example data_id. Examples of logging:

Could not find trigger router for trigger hist of {}. Skipped {} events starting with data id of {}

Could not find a trigger history row for the table {} for data_id {}. "Attempting" to generate a new trigger history row

A captured data row could not be matched with an existing trigger history row and we could not find a matching trigger. The data_id of {} (table {}) will be ignored

There was a mismatch between the data table name {} and the trigger_hist table name {} for data_id {}. Attempting to look up a valid trigger_hist row by table name

Invalid router type of '{}' configured on router '{}'. Using default router instead.

Ignoring data captured for table '{}' because there is no trigger router configured for it. If you removed or disabled the trigger router, you can disregard this warning. Starting with data id {} and trigger hist id {}, there were {} occurrences.
Steps To ReproduceStop the router service and control it manually. Capture some data for a mytest table, then manipulate the system tables to setup the different problem scenarios. Here are 7 scenarios:

1. update sym_router set router_type = 'badtype' where router_id = 'server waits for pull from client';

2. update sym_trigger_router set enabled = 0 where trigger_id = 'mytest';

3. delete sym_trigger_router where trigger_id = 'mytest';

4. update sym_data set trigger_hist_id = 9999999 where table_name = 'mytest';

5. update sym_data set trigger_hist_id = 9999998, table_name = 'invalid' where table_name = 'mytest';

6. update sym_data set table_name = 'invalid' where table_name = 'mytest';

7. After batch is extracted and OK'ed, then disable the trigger router, clear staging, and view the batch CSV

TagsNo tags attached.

Activities

There are no notes attached to this issue.

Related Changesets

SymmetricDS: 3.11 dcde200b

2019-12-12 13:09:07

admin

Details Diff
0004204: Efficient logging of trigger hist and trigger router problems
0004204
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/route/DataGapRouteReader.java Diff File
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/IDataService.java Diff File
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/DataExtractorService.java Diff File
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/DataService.java Diff File
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/RouterService.java Diff File
add - symmetric-core/src/main/java/org/jumpmind/symmetric/util/CounterStat.java Diff File

SymmetricDS: 3.11 e306736a

2019-12-12 13:33:33

admin

Details Diff
0004204: Efficient logging of trigger hist and trigger router problems
0004204
mod - symmetric-core/src/test/java/org/jumpmind/symmetric/route/DataGapRouteReaderTest.java Diff File

SymmetricDS: 3.11 b2726548

2019-12-12 14:05:57

admin

Details Diff
0004204: Efficient logging of trigger hist and trigger router problems
0004204
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/DataService.java Diff File

Issue History

Date Modified Username Field Change
2019-12-12 13:04 elong New Issue
2019-12-12 13:04 elong Status new => assigned
2019-12-12 13:04 elong Assigned To => elong
2019-12-12 13:09 elong Status assigned => resolved
2019-12-12 13:09 elong Resolution open => fixed
2019-12-12 13:09 elong Fixed in Version => 3.11.3
2019-12-12 14:00 admin Changeset attached => SymmetricDS 3.11 e306736a
2019-12-12 14:00 admin Changeset attached => SymmetricDS 3.11 dcde200b
2019-12-12 15:00 admin Changeset attached => SymmetricDS 3.11 b2726548
2020-01-02 09:42 admin Status resolved => closed