oli's blog

We found a pretty uncomfortable bug. It can be fixed easily by yourself or wait for the release of version 0.9.3 coming out soon. For more information see: here.

This seems to be a bug in v0.9.2 which happens when you have deadlock error messages in SHOW ENGINE INNODB STATUS output. (bug #139).

Hello

oh, I see. The installation advice for Ubuntu/Debian has a bug. libdigest-sha1-perl does not exits (any more?). I fixed the installation docu.

I’m going to deploy the new version of MPM on all my servers and i was wondering if there was a way to automatically delete or reload the cache file FromDualAgentCache.hostname.cache when we upgrade to the new version?

The mpm cache file is automatically loaded from the mpm agent to the Zabbix service at every run. After the load it is automatically shrinked/deleted again. So there is no need to reload or delete this file.>/p>

In some rare case (with older releases) mpm got a hick-up with too big cache files and then it makes sense to completely delete them.

OK. Try to set log_ouput to table with:

SET GLOBAL log_output = 'table';

From throughput point of view I agree. What about from response time point of view? We fire a query once and never again (the same).

Hello Øystein,

Unfortunately I have to agree! MySQL is damn fast/cool and hardware nowadays as well. And having much RAM and fast multi-core CPU's sucks from a tuner point of view ;-)

Hi Massimo,

From my last 14 years experience as DBA and DB consultant (Oracle, MySQL, MS-SQL Server, PostgreSQL). I have seen several hundreds? different DB performance problems in these years and only few of them (1 upon 20? or even less) where real throughput problems.
Most of them where single query performance problems (including optimizer/optimizing and configuration problems).

Hello Øystein,

The high/bad standard deviation with MySQL 5.6 comes from some very high outlier in the beginning of the test. I did not delete this outlier because I have seen this as an unfair treatment to the other releases which did not show this phenomena.

Hello Stephane,

Sorry, I cannot completely follow you what you want me to do. But please feel free to reproduce. All needed information are available I think!

Hi Joffrey,

The easy answer first: 5 - 15 iterations until it got a stable response time and then I took the most optimistic value. Not very scientific, I know... But I think good enough for a reliable statement.

There are many different possibilities how you can achieve inconsistencies between Master and Slave in a MySQL replication, intentional and non-intentional ones. How to achieve them is not the topic of this article.

Has this ever worked before (with < 2.2)?

Error 1305 means, that the agent cannot connect to the zabbix server. We verify: ZabbixServer, ZabbixPort and Hostname

It looks for me like check delivers an empty string and expects an int or decimal. One has to check what check delivers exactly and why. Debugging in the fpmmm agent should help on this…

[07:51:52] shyperson: I would suggest to --insert the rule instead of --apendING
[07:52:15] shyperson: Just to make sure there are no other rules allowing mysqlport before

About

glbd is a simple TCP connection balancer made with scalability and performance in mind. It was inspired by pen, but unlike pen its functionality is limited only to balancing generic TCP connections.

Hello Shinguz,

Pay attention: Your script is a bit too restrictive. It will IMHO also close the port for the SST when you use the wsrep_sst_methode = mysqldump. Possibly you should restrict it to the Load Balancer IP or allow access at least from the possible donors.

I was recently told that it would be better to use REJECT than DROP:

Since MySQL 5.1.43 timestamp is not allowed as partition key any more [ 1 ]. Thus we can do it as follows: