View Issue Details

IDProjectCategoryView StatusLast Update
0003592SymmetricDSImprovementpublic2018-06-05 15:30
ReportermmichalekAssigned Tommichalek 
Prioritynormal 
Status closedResolutionfixed 
Product Version3.8.0 
Target Version3.8.36Fixed in Version3.8.36 
Summary0003592: Log expiration of data gaps at info level
DescriptionEntries in sym_data_gap will expire after 20 minutes (by default) if no data shows up in those gaps. It is valid to expire a gap if data will *never* show up in the gap (due to something like a db transaction rollback). But data could get bypassed if a gap prematurely gets expired and later data_id's show up in that range. We will log at info when this happens so users can manage this setting properly.

When logging levels are at INFO, at most one log message will be emitted for expired gaps:

2018-06-01 15:27:51,564 INFO [corp-000] [DataGapFastDetector] [corp-000-job-1] Expired 2 data gap(s) between data_id 354 and 370 and between create_time 2018-06-01 15:15:08.275 and 2018-06-01 15:15:08.275

Relationships

related to 0003559 closedmmichalek Log expiration of data gaps at info level 

Activities

There are no notes attached to this issue.

Related Changesets

SymmetricDS: 3.8 5da3508b

2018-06-01 15:47:44

mmichalek

Details Diff
0003592: Log expiration of data gaps at info level
0003592
mod - symmetric-core/src/main/java/org/jumpmind/symmetric/route/DataGapFastDetector.java Diff File

Issue History

Date Modified Username Field Change
2018-06-01 15:35 mmichalek New Issue
2018-06-01 15:35 mmichalek Status new => assigned
2018-06-01 15:35 mmichalek Assigned To => mmichalek
2018-06-01 15:35 mmichalek Issue generated from: 0003559
2018-06-01 15:47 mmichalek Relationship added related to 0003559
2018-06-01 15:48 mmichalek Status assigned => resolved
2018-06-01 15:48 mmichalek Resolution open => fixed
2018-06-01 15:48 mmichalek Fixed in Version => 3.8.36
2018-06-01 16:00 mmichalek Changeset attached => SymmetricDS 3.8 5da3508b
2018-06-05 15:30 mmichalek Status resolved => closed