wsrep_incoming_addresses status variable empty
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MySQL patches by Codership |
Confirmed
|
Undecided
|
Unassigned | |||
5.5 |
New
|
Undecided
|
Unassigned | |||
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC | Status tracked in 5.6 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
New
|
Undecided
|
Unassigned |
Bug Description
Seems like AUTO method for wsrep_node_
mysql> show variables like 'wsrep_%address%';
+------
| Variable_name | Value |
+------
| wsrep_cluster_
| wsrep_node_address | 10.0.1.5 |
| wsrep_node_
| wsrep_sst_
+------
4 rows in set (0.00 sec)
mysql> show status like 'wsrep%address%';
+------
| Variable_name | Value |
+------
| wsrep_incoming_
+------
1 row in set (0.00 sec)
mysql> show variables like '%version%';
+------
| Variable_name | Value |
+------
| innodb_version | 5.6.15-rel62.0 |
| protocol_version | 10 |
| slave_type_
| version | 5.6.15-56-log |
| version_comment | Percona XtraDB Cluster (GPL), Release 25.2, Revision 645, wsrep_25.2.r4027 |
| version_
| version_compile_os | Linux |
+------
7 rows in set (0.00 sec)
mysql> show status like 'wsrep_
+------
| Variable_name | Value |
+------
| wsrep_provider_
+------
1 row in set (0.00 sec)
All three nodes have explicitly set wsrep_node_address.
The only way to get wsrep_incoming_
wsrep_node_
mysql> show status like 'wsrep%add%';
+------
| Variable_name | Value |
+------
| wsrep_incoming_
+------
1 row in set (0.00 sec)
The same status variable works automatically in 5.5 cluster even if both wsrep_node_address and wsrep_node_
So, to summarize, not setting wsrep_node_ incoming_ address leads to invalid address. Isn't that right.
value of wsrep_incoming_