[MDEV-6618] Consistency compromized after a CREATE TABLE command failed Created: 2014-08-21  Updated: 2015-03-17  Resolved: 2015-03-17

Status: Closed
Project: MariaDB Server
Component/s: wsrep
Affects Version/s: 5.5.37-galera
Fix Version/s: 5.5.43-galera, 10.0.17-galera

Type: Bug Priority: Major
Reporter: Lorenzo Assignee: Nirbhay Choubey (Inactive)
Resolution: Duplicate Votes: 0
Labels: crash, create_table, galera
Environment:

CentOS 6.5 x86_64
Galera Cluster installed from MariaDB repository
3 node with HAProxy to balance read (3 nodes) and write (1 node)

Attachments: File galera_cluser_hp8.log    

 Description   

2 of 3 nodes close server due to consistency compromized, after a CREATE TABLE command failed.
The sql comand was:
CREATE TABLE tab_test_tmp LIKE tab_test
It failed because the table tab_test didn't exist.
I attached the detailed log of a failed node.
My question is: why this failed sql command has been "replicatated" to other cluster node, if the command failed?

I can't reproduce the error because I don't have a testing cluster.

 Comments   
Comment by Nirbhay Choubey (Inactive) [ 2015-03-17 ]

Duplicate : MDEV-7673

Generated at Thu Feb 08 07:13:16 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.