Node1 fails, write node2 and node1 runs again, synchronize data node2

13 views
Skip to first unread message

Daniel Alberto Gonzalez Gomez

unread,
Apr 20, 2016, 8:41:35 AM4/20/16
to codership
Hello everyone


I have MariaDB and galley running , creating tables or records in any node are replicated seamlessly into the other. But to drop a node and want to write to the other will not let me :

writing in
MariaDB [playground]> INSERT INTO playground.equipment (type, quant, color) VALUES ("slide", 2, "blue");
ERROR 1047 (08S01): WSREP has not yet prepared node for application use

When I return to take the first node, it allows the creation of the registry without problems


It can be done for example if it falls a nodo1 to post on node2 , node1 run again when changes made to node2 is replicated ?



Nodo1 IP: 192.168.66.11

/etc/mysql/conf.d/cluster.cnf


[mysqld]
query_cache_size=0
binlog_format=ROW
default-storage-engine=innodb
innodb_autoinc_lock_mode=2
query_cache_type=0
bind-address=0.0.0.0

# Galera Provider Configuration
wsrep_provider=/usr/lib/galera/libgalera_smm.so
#wsrep_provider_options="gcache.size=32G"

# Galera Cluster Configuration
wsrep_cluster_name="test_cluster"
wsrep_cluster_address="gcomm://192.168.66.11,192.168.66.22"

# Galera Synchronization Congifuration
wsrep_sst_method=rsync
#wsrep_sst_auth=user:pass

# Galera Node Configuration
wsrep_node_address="192.168.66.11"
wsrep_node_name="NODO1"


Nodo2 IP: 192.168.66.22

/etc/mysql/conf.d/cluster.cnf




[mysqld]
query_cache_size=0
binlog_format=ROW
default-storage-engine=innodb
innodb_autoinc_lock_mode=2
query_cache_type=0
bind-address=0.0.0.0

# Galera Provider Configuration
wsrep_provider=/usr/lib/galera/libgalera_smm.so
#wsrep_provider_options="gcache.size=32G"

# Galera Cluster Configuration
wsrep_cluster_name="test_cluster"
wsrep_cluster_address="gcomm://192.168.66.22,192.168.66.11"

# Galera Synchronization Congifuration
wsrep_sst_method=rsync
#wsrep_sst_auth=user:pass

# Galera Node Configuration
wsrep_node_address="192.168.66.22"
wsrep_node_name="NODO2"




Reply all
Reply to author
Forward
0 new messages