PXC recovery doesn't always succeed when stopping/restarting node
General
Escalation
General
Escalation
Description
Environment
None
Smart Checklist
Activity
Show:
Julia Vural March 4, 2025 at 9:27 PM
It appears that this issue is no longer being worked on, so we are closing it for housekeeping purposes. If you believe the issue still exists, please open a new ticket after confirming it's present in the latest release.
Kamil Holubicki July 26, 2024 at 1:03 PM
To be verified
Won't Do
Details
Details
Assignee
Unassigned
UnassignedReporter
KennTLabels
Affects versions
Priority
MediumSmart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Created October 26, 2017 at 9:13 AM
Updated March 4, 2025 at 9:27 PM
Resolved March 4, 2025 at 9:27 PM
From
PXC recovery doesn't always succeed when we run cluster_mess
https://github.com/percona/pmm-demo/blob/master/loader/cluster_mess
Script stops, starts, deletes datadir - with SST it should just work
Environment
3 node cluster
pxc56-1 / pxc56-2 / pxc56-3 - 5.6.37
pxc57-1 / pxc57-2 / pxc57-3 - 5.7.19
ProxySQL configured for singlewrite using proxysql-admin on the -1 nodes - version 1.4.3
1 Writer
2 Readers
sysbench
on -1 nodes - via /tmp/proxysql.sock
schema names of innodb, innodb_icp ,etc
on -2, -3 nodes - via /var/lib/mysql/mysql.sock
schema names of innodb_2, innodb_3
to ensure there aren't write conflicts
I have them down right now because sometimes it caused nodes to leave the cluster