docs: report SYNC replication failure as a notification - #1745
Open
as51340 wants to merge 1 commit into
Open
Conversation
A transaction that cannot reach every SYNC replica is still committed on the main and on every reachable replica, so memgraph/memgraph#4601 stopped failing the query and reports the failure as a WARNING notification with the code SyncReplicationFailure instead. ReplicationException is kept only for the case where the transaction was rolled back everywhere (STRICT_SYNC two-phase commit abort). - query-metadata: add the SyncReplicationFailure code and a section on commit-time notifications, which reach the client in the summary of the last query of an implicit transaction or of the explicit COMMIT - how-replication-works: SYNC failures now succeed with a notification; name ReplicationException explicitly in the STRICT_SYNC section - help-center errors: split notification from exception by transaction outcome rather than by replica mode - setup-ha-cluster-k8s: rolling upgrades no longer require applications to catch a replication exception on SYNC writes - release-notes: v3.13.0 breaking change entry
as51340
requested review from
Josipmrden,
gitbuda and
vpavicic
as code owners
September 2, 2026 05:43
as51340
added
the
feature
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Release note
A transaction that cannot reach every SYNC replica is still committed on the main instance and on every reachable replica, so it no longer fails the query. The failure is now reported as a
WARNINGnotification with the codeSyncReplicationFailure, delivered in the summary of the last query of an implicit transaction or of the explicitCOMMIT.ReplicationExceptionis kept only for the case where the transaction was actually rolled back everywhere (STRICT_SYNC two-phase commit abort). This is a client-visible breaking change for applications that caught the replication exception around writes.Related product PRs
Checklist:
bugfixorfeaturelabel, based on the product PR type you're documentingnode_modulesis not installed in this worktree