Comments - Galera errors in mysqld.log but works OK

7 years, 11 months ago Andy Ferretti

Thanks for the analysis and reference. I copied the example notify script and changed the user, password, and host parameters to ensure a valid connection. I chose not to use root as the notify account. I modified the wsrep_notify_cmd to point to the new script and bounced each node. The notify function was executed and the error messages ceased. This was my primary goal and was addressed by the information you provided. I have a couple of follow-up items and can create additional entries if recommended. 1. As I created the user and changed the password, I noticed that the new password worked on only one node. I found this article indicating that I need to use DDL to change the password: http://galeracluster.com/documentation-webpages/userchanges.html. I thought that since I was using the "SET PASSWORD" command, I was using DDL. I had to execute this on each node in order to have the same password on each node. 2. Looking at the sample notify script, it appear that it drops and creates the schema every time. We had some node crashes due to a validation script that was dropping/creating tables on multiple nodes a the same time. It caused two nodes to crash. I know this is just a sample and I would be free to change it. I'm just wondering if I understand correctly and whether anyone has reported problems with this.

 
7 years, 11 months ago Ian Gilfillan

1) No, SET statements are not normally considered DDL,

2) If you are getting crashing errors, please report as a bug, as those shouldn't be happening.

 
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.