wsrep_incoming_addresses status variable empty

Bug #1266750 reported by Przemek on 2014-01-07
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Undecided
Unassigned
5.5
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_incoming_address is not working in cluster based on MySQL 5.6.

mysql> show variables like 'wsrep_%address%';
+-----------------------------+------------------------------------+
| Variable_name | Value |
+-----------------------------+------------------------------------+
| wsrep_cluster_address | gcomm://10.0.1.4,10.0.1.5,10.0.1.6 |
| wsrep_node_address | 10.0.1.5 |
| wsrep_node_incoming_address | AUTO |
| wsrep_sst_receive_address | AUTO |
+-----------------------------+------------------------------------+
4 rows in set (0.00 sec)

mysql> show status like 'wsrep%address%';
+--------------------------+-------+
| Variable_name | Value |
+--------------------------+-------+
| wsrep_incoming_addresses | ,, |
+--------------------------+-------+
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_conversions | |
| version | 5.6.15-56-log |
| version_comment | Percona XtraDB Cluster (GPL), Release 25.2, Revision 645, wsrep_25.2.r4027 |
| version_compile_machine | x86_64 |
| version_compile_os | Linux |
+-------------------------+----------------------------------------------------------------------------+
7 rows in set (0.00 sec)

mysql> show status like 'wsrep_provider_version';
+------------------------+-----------+
| Variable_name | Value |
+------------------------+-----------+
| wsrep_provider_version | 3.2(r170) |
+------------------------+-----------+
1 row in set (0.00 sec)

All three nodes have explicitly set wsrep_node_address.

The only way to get wsrep_incoming_addresses status variable working is to set explicitly in my.cnf:

wsrep_node_incoming_address=10.0.1.4

mysql> show status like 'wsrep%add%';
+--------------------------+-----------------+
| Variable_name | Value |
+--------------------------+-----------------+
| wsrep_incoming_addresses | 10.0.1.4:3306,, |
+--------------------------+-----------------+
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_incoming_address are not set explicitly.

Tags: 5.6 Edit Tag help

So, to summarize, not setting wsrep_node_incoming_address leads to invalid
value of wsrep_incoming_address. Isn't that right.

Przemek (pmalkowski) wrote :

In PXC 5.5 setting wsrep_node_incoming_address is NOT necessary for the wsrep_incoming_address to work well (auto mode works), while in 5.6 it is the only way to make it work.
So it is about regression in 5.6.

Ilin (itatabitovski) wrote :

In PXC 5.6 I have wsrep_node_address set in my.cnf

wsrep_node_incoming_address should use wsrep_node_address by default

If I set bind_address to anything other than the default * I get the IP address in wsrep_incoming_addresses. When bind_address is not set or * then the addresses are missing.

Yan Zhang (yan.zhang) wrote :

@Przemek

I check code that wsrep5.5 and wsrep5.6 have the same code to guess wsrep_node_incoming_address.

Could you check the error log? Because if wsrep_node_incoming_address is not guess successfully, a warning log starts with "Guessing address for incoming client connections:" will be printed out.

 and could you provide your bind-address with command ``` show variables like 'bind_address'; ```, because if bind_address is set to 127.0.0.1 then wsrep_node_incoming_address will be empty too.

Frederic Descamps (lefred) wrote :

percona-xtradb-cluster-server-5.6 5.6.15-25.5-759.precise
percona-xtradb-cluster-galera-3.x 216.precise

wsrep_provider=/usr/lib/libgalera_smm.so
wsrep_cluster_address=gcomm://192.168.2.10,192.168.100.11,192.168.100.12,192.168.100.10
wsrep_node_address=192.168.2.11
wsrep_node_name=dbOffice2

grep -i bind /etc/mysql/my.cnf -> empty

grep -i Guessing logs/mysql/mysql-error.log | wc -l
0

mysql> show global status like 'wsrep_inco%';
+--------------------------+-------+
| Variable_name | Value |
+--------------------------+-------+
| wsrep_incoming_addresses | ,,, |
+--------------------------+-------+
1 row in set (0,00 sec)

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

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

Other bug subscribers