Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 10.0.14-galera
-
Fix Version/s: None
-
Component/s: Galera
-
Labels:
-
Environment:Ubuntu 12.04, 3 node cluster.
MariaDB Galera Cluster 10.0.14
Description
Hi,
My galera cluster crashed. It's a 3 node cluster.
The flow is like this:
First node01 died and tried to restart a couple of times, after that node03 died.
node02 was alone in the cluster and didn't really work cause I guess it didn't have quorum.
node01 and node03 couldn't start and join the cluster.
So then I killed node02 so I could start the cluster fresh.
To make this even more complicated, I have a service supervisor that tries to start the service when it's dead(until i stopped the supervisor). So the logs got a bit cluttered from all the start attempts.
Before I killed node02 I made sure the service supervisor didn't try to start the other nodes.
After I killed node02, I tried a normal start, that failed.
Then finally I started node02 with --wsrep-new-cluster, then it started, after that I started node03, after that node01.
I have attached the logs, and in the logs there are some errors related to table somedb_staging_api.bookings. Please note that that table was at that time a MyISAM table.
And we have myisam replication turned off.
Is the myisam table the reason for the crash or something else?
Gliffy Diagrams
Attachments
Issue Links
- relates to
-
-
- Open
-
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions