View Revisions: Issue #6987

Back to Issue
Summary 0006987: Suppress first error when auto-resolving lines in batch (foreign key or deadlock), escalate on second error for the same line
Revision 2025-07-07 13:10 by elong
Description Suppress the first occurrence of a batch foreign key error so the auto resolver has a chance to recover from the error. When the user sees an error, they think they need to intervene instead of allowing the system to recover on its own. Some batches have multiple foreign key errors, which can take some time to auto resolve. Log the line number of the batch with the error, so it is easy to see the batch is advancing in the logs. The batch tables should show a status of LD and an error flag of 0. The process info should also be OK without a batch number to prevent the web console screens from displaying an indication of an error.
Revision 2025-07-11 19:52 by pbelov
Description Currently, when the user sees a batch with the Foreign Key error, they think they need to intervene.
If let be SymmetricDS (on versions 3.14+) already has logic to auto-resolve this data problem: it requests missing "parent" row data from the source node and recovers from most such errors automatically.
Some batches have multiple foreign key errors (not all on the same row), which can take some time to auto-resolve.

Change:
Suppress the first occurrence of a batch foreign key error so the auto resolver has a chance to recover from the error.
Log the line number of the batch with the error, so it is easy to see the batch is advancing (in the logs).
The batch tables should show a status of LD and an error flag of 0.
The process info should also be OK without a batch number to prevent the web console screens from displaying an indication of an error - until error is sustained (unsolvable).
Revision 2025-07-14 16:26 by pbelov
Description Currently, when the user sees a batch with the Foreign Key error (or a deadlock error), they think they need to intervene.
The SymmetricDS (versions 3.14 and higher) already has logic to auto-resolve such data problems. For foreign key errors it requests missing "parent" row data from the source node and recovers from most such errors automatically.
Some batches have multiple foreign key errors (not all on the same row), which can take some time to auto-resolve, but does not require intervention.

Change:
Suppress the first occurrence of a batch foreign key error so the auto resolver has a chance to recover from the error.
Log the line number of the batch with the error, so it is easy to see the batch is advancing (in the logs).
The batch tables should show a status of LD and an error flag of 0.
The process info should also be OK without a batch number to prevent the web console screens from displaying an indication of an error - until error is sustained (unsolvable).