MDEV-33175 applier FK check failure retrying #385
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Implementation of foreign key constraint check retrying for replication appliers Foreign key constraint checks may occaionally fail even though the constraints are not violated. There have been cases where e.g. the same transaction inserts in the parent table, and the next insert into child table fails in foreign key checks. The underlying reason for these failures is not known. This change adds retrying of constraint check in InnoDB. The number of retries is by default 1, and the number of retries can be controlled by a new system variable wsrep-applier-FK-failure-retries`. If the constraint check fails despite retries, the final retry prints out a warning with an error code and InnoDB system monitor output for further troubleshooting. Co-authored-by: Teemu Ollakka <[email protected]>
|
test_pr |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implementation of foreign key constraint check retrying for replication appliers
Foreign key constraint checks may occaionally fail even though the constraints are not violated. There have been cases where e.g. the same transaction inserts in the parent table, and the next insert into child table fails in foreign key checks. The underlying reason for these failures is not known.
This change adds retrying of constraint check in InnoDB. The number of retries is by default 1, and the number of retries can be controlled by a new system variable
wsrep-applier-FK-failure-retries`. If the constraint check fails despite retries, the final retry prints out a warning with an error code and InnoDB system monitor output for further troubleshooting.