Tag Info

New answers tagged

0

If you are using Galera with MySQL 5.6, log_slow_queries was removed. Here is what the MySQL 5.6 Documentation says on that option The --log-slow-queries option was removed in MySQL 5.6.1 (along with the log_slow_queries system variable). Instead, use the --slow_query_log option to enable the slow query log and the --slow_query_log_file=file_name option ...


1

I continued working on the problem, and put together a solution that worked for me. Solution This solution assumes that server-2 is the server with the broken replication. This solution needs to be mirrored if server-1 is the server that is broken. Disable incoming connections on both servers SHOW FULL PROCESSLIST; should only show a localhost ...


1

MDMarra is correct, this is not a question that can reasonably be answered definitively here (+1). You need to take a look at your application across all seven layers of the OSI model and then add redundancy at each level. You will most likely need input from all of the developers and admins involved. When management starts complaining about the price ...


4

This depends entirely on the architecture and availability options of the specific applications in use. Does your database support a clustered deployment? A mirrored/replicated deployment? Both? What are the caveats of each? What's the failover/recovery process? The resource allocation requirements? What about for your web app? Can that be clustered? Load ...


0

We had this problem too, and it took me a while to figure out what was going on because I managed to get Galera working at one point, then it failed again when I tried to repeat it all from scratch. The not-very-descriptive unknown error -141 appears to occur when spawned processes (such as SST backup runs) fail on startup, when they try to write to the ...


1

The MySQL replication happens through binlog. To the binlog only successful transactions will be written, so if a query fails on a master it won't appear in binlog. That means this kind of queries will not appear on replicas. If you have errors like replication stops on slave1 because there is no column for update (etc.) then that means your master and ...


2

I understand it can't or shouldn't be done. Am I right? I would say you are incorrect, in spite of the fact that what you are saying seems consistent with what's documented. A plain reading of the documentation notwithstanding, you can do this indefinitely, on an ongoing basis, as long as you don't expect Amazon to provide support for your non-standard ...


0

Well, in case anyone comes across this same error: I fixed it by installing a different version. Not too sure how I did it, but by using different yum repos, I managed to install a community version of MySQL, in which this works as expected



Top 50 recent answers are included