Skip to content

Bugfix: Unregister replication instance could lead to a deadlock #1170

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
katarinasupe merged 4 commits into from
Mar 5, 2025
Merged

Bugfix: Unregister replication instance could lead to a deadlock #1170

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
29c4b97
Unregister deadlock
as51340 Mar 3, 2025
c71b7e3
update wording
katarinasupe Mar 5, 2025
ab0fb94
fix typo
katarinasupe Mar 5, 2025
d41f226
Merge branch 'memgraph-3-1' into bugfix-unregister-deadlock
katarinasupe Mar 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion pages/clustering/high-availability.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -264,7 +264,11 @@ network communication could be set up incorrectly, etc. The user can remove the
UNREGISTER INSTANCE instanceName;
```

At the moment of registration, the instance that you want to unregister must not be MAIN because unregistering MAIN could lead to an inconsistent cluster state.
When unregistering an instance, ensure that the instance being unregistered is
**not** the MAIN instance. Unregistering MAIN can lead to an inconsistent
cluster state. Additionally, the cluster must have an **alive** MAIN instance
during the unregistration process. If no MAIN instance is available, the
operation cannot be guaranteed to succeed.

The instance requested to be unregistered will also be unregistered from the current MAIN's REPLICA set.

Expand Down