New answers tagged

0

MySQL has replication cabapilities, sure you has revised the MySQL documentation. This means that MySQL copies data from master to slave, not both directions. You proposed "just click a button", if you don't want a "do it yourself" solution maybe can try with a database tool like MySQL workbench. In any case it is dangerous to synchronize two databases ...


0

1) Although I prefer tcpdump myself I would ask what is the reason not to enable slow logs because it is not that big of an overhead. With reasonable thresholds it's actually very useful. If you want to be super cautious you can safely enable it with a conservative long_query_time and slowly dropping it. The variable is dynamic so you can change it on the ...


0

----- 2014-09-25 5.7.5 Milestone 15 -- Functionality Added or Changed -- Replication ----- When replicating from a master running a version earlier than MySQL 5.6.0 to a slave running MySQL 5.6.0 or later, the slave requires the master_uuid value, which is the server_uuid ( http://dev.mysql.com/doc/refman/5.7/en/replication-options.html#sysvar_server_uuid ) ...


0

You could do the following, provided that your sensor 6511 takes measurements reliably every 30 minutes (use instead the one that is most reliable). This will calculate measurements based on the recordings of that primary sensor used (in the main FROM, in this case 6511), show the exact date and time of such recording, also show an adjusted time in 30 min ...


3

While MySQL does not impose a password length limit, replication does. (I have not been able to find this in the MySQL documentation, but, empirically, it holds.) This is all the less obvious, because the longer password works for login but fails for replication. So, in the end, reducing the password to 32 characters solved the problem.



Top 50 recent answers are included