Nodebalanced MySQL

Hmm. Interesting question. Did you determine the private IP of the NodeBalancer? Is that allowed via the MySQL user's "host" field?

Also, I shared this question via social media to hopefully bring more eyes. I would love to know the answer to this too.

I just gave this a quick test this on fresh servers with loose MySQL permissions. No firewall rules were in place – if you're getting timed out errors I suspect that this is firewall related. Our Nodebalancer private range is 192.168.255.0/24, it's rare but your Nodebalancer private IP can change so we generally recommend whitelisting the whole range for dependent applications.

For my test configuration, I added a MySQL user as follows:

CREATE USER 'username'@'localhost' IDENTIFIED BY 'password';

GRANT ALL PRIVILEGES ON . TO 'username'@'localhost' WITH GRANT OPTION;

CREATE USER 'username'@'%' IDENTIFIED BY 'password';

GRANT ALL PRIVILEGES ON . TO 'username'@'%' WITH GRANT OPTION;

In my.cnf the bind address set to the respective private IPs.

From there I could connect with:

mysql -u username -h -p

The only caveat is that sometimes you'll hit one back and sometimes you'll hit the other. I used session stickiness 'none' and Nodebalancer algorithm set to Round Robin to ensure that I was hitting different backends on subsequent attempts.

Feel free to open a ticket with us if you'd like us to take a closer look at your configuration -- we can recap the solution here if needed.