blank space in wsrep_cluster_address are not valid

[Sergio Charrua]

Hello,

Not a support request, but instead a concern....

Apparently wsrep_cluster_address parameter in mariadb-server.cnf is sensitive to blank spaces.

For example, using the following line in all 3 nodes of the cluster:

wsrep_cluster_address="gcomm://10.X.Y.120, 10. X.Y.121, 10.X.Y .122"

(notice blank space between comma and IP address)

will make that only IP .120 can be bootstapped as primary node of the cluster. If I bootstrap any other node, and then start the other nodes, the cluster will fail and only 1 node (.120) will be available!

The reason is that (I suspect) the configuration file parser is splitting values by comma but not trimming blank spaces from the resulting values, and even if we set IP addresses but a comma is found, then Galera will use the value as a hostname instead of an IP address, making it searching for hostname " 10.242.17.121" instead of IP 10.242.17.121.

I agree that any other character added to an IP address should result that the value should be handled as a hostname. But there are no hostnames with blanks in it! :)

This should be addressed, because any standardised .INI file, or .CONF or .CFG file parser handles well blank spaces in these kind of values. So, why not Galera? 

I'm not sure if this limitation is related to MariaDB itself or if this is a Galera "issue" (emphasis on double quotes....) but this should be corrected and allow blank spaces between IP addresses, helping anyone to read the parameter in a more easier way (depending on the terminal fonts, it tends to be hard to differentiate a comma from a dot "." between 3 or more IP addresses, and blank spaces help a lot!)

Hope this helps !

Sérgio