An explicitly set wsrep_node_incoming_address may make SHOW STATUS LIKE 'wsrep_incoming_addresses' return a portless address

[Brian Fraser]

Title's a mouthful. This is basically an enhancement request to this: https://bugs.launchpad.net/galera/+bug/1003908

> SHOW STATUS LIKE 'wsrep_incoming_addresses';

gives precedence to wsrep_node_incoming_address, which is good, but since the recommended practice is setting wsrep_node_incoming_address to an IP without a port section, it makes the status return something like '10.11.12.77,10.11.12.77,10.11.12.77', which is useless.

So, if the address doesn't have a port bit, would it be possible to return the address + mysqld_port? This will make node autodiscovery in Percona Toolkit a breeze.

[Brian Fraser (fraserbn)]

Also, changing the docs to use addr:port would be fantastic.

[Alex Yurchenko (ayurchen)]

> recommended practice is setting wsrep_node_incoming_address to an IP without a port section

Since when is it recommended?

[Brian Fraser (fraserbn)]

Every single example I could google has it with just the address. I admit that's not the same as "recommended" -- but how many people are going to dig up the docs and find out that you an put addr:port?

[Alex Yurchenko (ayurchen)]

Pushed in lp:codership-mysql/5.5 r3841 - fixes to use mysqld_port when no port (no ':') is found in wsrep_node_incoming_address. wsrep_node_incoming_address however remains unchanged - not sure what would be the right thing to do in that case.

[Seppo Jaakola (seppo-jaakola)]

merged the fix into wsrep-23 branch: http://bazaar.launchpad.net/~codership/codership-mysql/5.5-23/revision/3843

[Alex Yurchenko (ayurchen)]

fix released in 23.7.3

[Shahriyar Rzayev (rzayev-sehriyar)]

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

[Shahriyar Rzayev (rzayev-sehriyar)]

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