View Revisions: Issue #6685

All RevisionsBack to Issue
Summary 0006685: Purge Service recaptures an Insert for stranded data after record had been deleted
Revision 2024-12-26 22:08 by pbelov
Description Purge Service recaptures an Insert for stranded data after record had been deleted
If a transaction is active for longer than the duration of the parameter routing.stale.dataid.gap.time.ms, data will be marked as stranded.
Data in such long database transaction will not be processed normally, instead this data will go through the recapture process when the purge job runs.
If there is a stranded Insert (or Update) but the original row had been deleted, then the Purge job will incorrectly keep the original insert (or update) command.
This results in data being present on target database and not at the source.
Revision 2024-12-23 19:36 by mdrouard
Description The purge service is missing deletes when trying to recapture data from a data gap on long running transactions.
If a transaction is active for longer than the duration of the parameter routing.stale.dataid.gap.time.ms, data will be marked as stranded.
Data that is processed during this time will not be inserted normally, instead this data will be processed as a recapture when the purge job runs.
If there is an insert and then a delete of a row that both are outside of the routing.stale.dataid.gap.time.ms length then the delete will not be properly processed in the recapture.
This can result in data being present on target database and not source
Revision 2024-12-23 19:36 by mdrouard
Description The purge service is missing deletes when trying to recapture data from a data gap on long running transactions.
If a transaction is active for longer than the duration of the parameter routing.stale.dataid.gap.time.ms, data will be marked as stranded.
Data that is processed during this time will not be inserted normally, instead this data will be processed as a recapture when the purge job runs.
If there is an insert and then a delete of a row that both are outside of the routing.stale.dataid.gap.time.ms length then the delete will not be properly processed in the recapture.