New answers tagged my.cnf
In a Galera cluster, any node can play the part of a Master node. Such a node can execute DML (INSERTs, UPDATEs, and DELETEs). If DML statements are spread across multiple Master nodes and are targeting the same tables, you must expect log conflicts. Why ? Galera wsrep libraries were designed to commit DML changes if all nodes in a cluster are ready to do ...
This information may not be of interest to the DBA. If the application is handling conflicts correctly, there is no need to log them. It would be expected behaviour. You would only enable this level of logging if you were debugging a specific issue. Otherwise it would generate a lot of spam in the logs.
The answer is indeed the SQL Nodes - the key factor is related to the client - the setting doesn't apply until you close the client session and reopen it
On OS X, here is a simple method to check whether your file is read. Run: sudo fs_usage | grep my.cnf This will report any filesystem activity in real-time related to that file. In another Terminal, restart your MySQL/MariaDB server, e.g. brew services restart mysql # or: mariadb On terminal with fs_usage, the proper location should be shown, e.g. 15:...
Top 50 recent answers are included