gmcast does not bind outgoing connections to listen addr
Bug #1240964 reported by
shinguz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Galera | Status tracked in 3.x | |||||
2.x |
Fix Committed
|
Undecided
|
Unassigned | |||
3.x |
Fix Released
|
Medium
|
Yan Zhang | |||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Fix Released
|
Medium
|
Unassigned | |||
5.6 |
Fix Released
|
Medium
|
Unassigned |
Bug Description
2 Galera nodes on 1 server with 2 interfaces on port 3306
node 1 starts properly (gcomm://)
when node 2 starts node 1 falls into state initialized/
This seems to be related somehow to SST (mysqldump).
Changed in galera: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in galera: | |
assignee: | nobody → Yan Zhang (yan.zhang) |
milestone: | none → 25.3.6 |
status: | Confirmed → In Progress |
Changed in galera: | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
Similar case reported in https:/ /groups. google. com/forum/ #!topic/ codership- team/_DCRJIgKY2 0.
It appears that if gmcast.listen_addr is configured to certain address, local connection point for outgoing connections is not bound to listen address. If OS has multiple interfaces with IP addresses in the same subnet, it may happen that OS picks wrong IP for local connection point and other nodes see connections originating from IP address which is not listened to.