Behavior of pc.ignore_sb in Galera 3
Bug #1229632 reported by
Raghavendra D Prabhu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Galera | Status tracked in 3.x | |||||
3.x |
Invalid
|
Undecided
|
Teemu Ollakka |
Bug Description
The behavior of pc.ignore_sb has changed in galera. Setting it as part of wsrep_cluster_
Changed in galera: | |
assignee: | nobody → Teemu Ollakka (teemu-ollakka) |
milestone: | none → 3.1 |
To post a comment you must log in.
Could not reproduce this:
Command to start mysqld:
/run/shm/ galera/ local1/ mysql/sbin/ mysqld --defaults- file=/run/ shm/galera/ local1/ mysql/etc/ my.cnf --user=teemu --basedir= /run/shm/ galera/ local1/ mysql --datadir= /run/shm/ galera/ local1/ mysql/var --plugin- dir=lib/ mysql/plugin --pid-file= /run/shm/ galera/ local1/ mysql/var/ mysqld. pid --port=3311 --socket= /run/shm/ galera/ local1/ mysql/var/ mysqld. sock --skip- external- locking --log_error= /run/shm/ galera/ local1/ mysql/var/ hp.err --default- storage- engine= InnoDB --wsrep_ provider= /run/shm/ galera/ local1/ galera/ lib/libgalera_ smm.so --wsrep_ cluster_ address= gcomm:/ /?pc.ignore_ sb=1&gmcast. listen_ addr=tcp: //gw:10011 --wsrep_ start_position= 9ac15fea- 2513-11e3- bcd4-33878a9222 ca:0
Log shows: 2513-11e3- b799-1ef476e847 f8, 'tcp:// 192.168. 3.254:10011' ) listening at tcp://192. 168.3.254: 10011
2013-09-24 15:21:41 8573 [Note] WSREP: (de6aaaa2-
$ netstat -natp |grep 10011
tcp 0 0 192.168.3.254:10011 0.0.0.0:* LISTEN 8573/mysqld
Joining another node to cluster goes as usual.