Garbd IP is not visible in wsrep_incoming_addresses status variable

Description

Garbd IP is not visible in wsrep_incoming_addresses status variable. Shows up only extra comma with empty string.
Testcase
1) start 2 node cluster.
2) start garbd daemon.

PXC: root@localhost ((none)) > show global status like '%wsrep_cluster_size%';
---------------------------+

Variable_name

Value

---------------------------+

wsrep_cluster_size

3

---------------------------+
1 row in set (0.00 sec)

PXC: root@localhost ((none)) > show global status like '%wsrep_incoming_addresses%';
------------------------------------------------------------------+

Variable_name

Value

------------------------------------------------------------------+

wsrep_incoming_addresses

,10.202.236.8:3306,10.202.236.184:3306

------------------------------------------------------------------+
1 row in set (0.00 sec)
 

More over if we tune https://galeracluster.com/library/documentation/mysql-wsrep-options.html#wsrep-node-incoming-address variable other than AUTO the value is  shown blindly, i.e. 

wsrep_node_incoming_address=“10.202.236.68,10.202.236.8:3306,10.202.236.184”
PXC: root@localhost ((none)) > show global status like '%wsrep_incoming_addresses%';
-----------------------------------------------------------------------------------------------------------+

Variable_name

Value

-----------------------------------------------------------------------------------------------------------+

wsrep_incoming_addresses

10.202.236.68,10.202.236.8:3306,10.202.236.184

-----------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)
 

but even if I place a non-existent IP

wsrep_node_incoming_address=“10.202.236.68,10.202.236.8:3306,10.202.236.184,1.1.1.1:3306”

We see it printed in the status: 
PXC: root@localhost ((none)) > show global status like '%wsrep_incoming_addresses%';
-----------------------------------------------------------------------------------------------------------+

Variable_name

Value

-----------------------------------------------------------------------------------------------------------+

wsrep_incoming_addresses

10.202.236.68,10.202.236.8:3306,10.202.236.184,1.1.1.1:3306

-----------------------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)
 

I think we have 3 potential solutions: 

  • add wsrep_node_address variable to garbd daemon

  • remove the empty value from wsrep_incoming_addresses

  • grab the IP when garbd is connecting and report it correctly in wsrep_incoming_addresses

Environment

None

Smart Checklist

Activity

Kamil Holubicki April 20, 2022 at 1:18 PM

As 'wsrep_incoming_addresses' is useful for detecting cluster nodes able to process incoming workload, reporting garbd there makes no point.
Fixed string formating to avoid not necessary commas.

Kamil Holubicki April 20, 2022 at 8:07 AM

Lalit Choudhary January 5, 2022 at 12:19 PM

Hi 

Thank you for the report.

Done

Details

Assignee

Reporter

Time tracking

1d 1h 55m logged6h 8m remaining

Priority

Smart Checklist

Created October 29, 2021 at 12:58 PM
Updated March 6, 2024 at 9:04 PM
Resolved April 25, 2022 at 9:50 AM