Skip to content

MDEV-30516 : Assertion `wsrep_cluster_address[0]' failed in void wsre… #510

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.

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

Open
wants to merge 1 commit into
base: 10.6
Choose a base branch
from

Conversation

janlindstrom
Copy link

…p_create_rollbacker()

In wsrep_cluster_address_update there is possibility of race condition if two connections concurrently set wsrep_cluster_address. Concurrent change is possible because stopping replication requires to unlock LOCK_global_system_variables mutex.

Fix is to use existing local variable tmp containing set wsrep_cluster_address on also when creating rollbacker threads. This variable is set when mutex to
LOCK_global_system_variables is still held.

@janlindstrom janlindstrom self-assigned this Jun 23, 2025
…p_create_rollbacker()

In wsrep_cluster_address_update there is possibility of race
condition if two connections concurrently set wsrep_cluster_address.
Concurrent change is possible because stopping replication
requires to unlock LOCK_global_system_variables mutex.

Fix is to use existing local variable tmp containing set
wsrep_cluster_address on also when creating rollbacker threads.
This variable is set when mutex to LOCK_global_system_variables
is still held.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant