View Revisions: Issue #3559
| Summary | 0003559: Log expiration of data gaps at info level | ||
|---|---|---|---|
| Revision | 2018-05-10 17:57 by mmichalek | ||
| Description | Entries 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. |
||
| Revision | 2018-06-01 19:33 by mmichalek | ||
| Description | Entries 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 |
||