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
Steps To Reproduce 0. Alter routing.stale.dataid.gap.time.ms to be a period that you are willing to wait to create a stranded data (data gap).
1. Turn off auto-commit on SQL transactions (for testing).
2. Run an insert on a source table and do not commit just yet.
3. Wait for time, exceeding the routing.stale.dataid.gap.time.ms value.
4. Commit the Insert transaction.
5. Run a Delete command targeting the same record that was inserted and commit immediately.
6. Allow the Routing job to run and pick up the data gap.
7. Run manually or wait until the Purge Outgoing job runs.
9. Select from the table on source and client and compare the difference. Observe record missing on the source database but present on the target.
Revision 2024-12-23 19:36 by mdrouard
Steps To Reproduce 0. Alter routing.stale.dataid.gap.time.ms to be a period that you are willing to wait to create a data gap.
1. Turn off autocommit on SQL transactions.
2. Run an insert on a source table and do not commit.
3. Run a delete on the record that was inserted after a short period and do not commit.
4. Wait for the roting stale data gap time to pass.
5. Insert a record on a different console and commit it normally before committing the slow transaction
6. Allow routing to run on the fast transaciton and pick up the data gap
7. Commit the transaction that was slow running.
8. Allowing routing/purge service to run
9. Select from the table on source and client and compare the difference.