setting gmcast.listen_addr manually does not allow nodes own address in gcomm address list
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Galera | Status tracked in 3.x | |||||
2.x |
Fix Released
|
High
|
Teemu Ollakka | |||
3.x |
Fix Released
|
High
|
Teemu Ollakka | |||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Fix Released
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Undecided
|
Unassigned | |||
percona-xtradb-cluster-galera-2.x (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Having specified gmcast.listen_addr manually in provider options
wsrep_provider_
and having node's own IP address in gcomm address list
wsrep_cluster_
causes gcomm to fail in connecting cluster with following message:
130111 13:53:46 [ERROR] WSREP: failed to open gcomm backend connection: 22: connect address points to listen address 'tcp://
at gcomm/src/
130111 13:53:46 [ERROR] WSREP: gcs/src/
The reason for this is a check in GMCast constructor which does not allow having listen address in peer address list. This check should be removed and own listen address in address list should just be skipped.
Related branches
- David Bennett: Pending requested
- Diff: 0 lines
This can affect more when setting more than one instance on same box.