gmcast does not bind outgoing connections to listen addr

Bug #1240964 reported by shinguz on 2013-10-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Galera
Status tracked in 3.x
2.x
Undecided
Unassigned
3.x
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/non-Primary.

This seems to be related somehow to SST (mysqldump).

shinguz (oli-sennhauser) wrote :
shinguz (oli-sennhauser) wrote :
shinguz (oli-sennhauser) wrote :
shinguz (oli-sennhauser) wrote :
Teemu Ollakka (teemu-ollakka) wrote :

Similar case reported in https://groups.google.com/forum/#!topic/codership-team/_DCRJIgKY20.

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.

summary: - Donor falls to state Initialized/non-Primary
+ gmcast does not bind outgoing connections to listen addr
Changed in galera:
status: New → Confirmed
importance: Undecided → Medium
Yan Zhang (yan.zhang) on 2014-05-15
Changed in galera:
assignee: nobody → Yan Zhang (yan.zhang)
milestone: none → 25.3.6
status: Confirmed → In Progress
Yan Zhang (yan.zhang) on 2014-05-15
Changed in galera:
status: In Progress → Fix Committed

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1084

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers