Recently, I did some maintenance on Innotop and I merged several pull requests including one to support MySQL 8.0 (thank you yoku0825 for the contribution).
As you know, Innotop is written in Perl and to be able to use it
with MySQL 8.0, you need to have Perl DBD
for MySQL compatible with MySQL 8.0 too (a driver that support
the new default authentication plugin,
caching_sha2_password).
If you are using Fedora 29, I created such package and you can download it here: …
[Read more]What about an hackathon to fix several issues in Innotop during this Fosdem 2016 edition ?
As the MySQL & Friends Devroom is on Saturday, Sunday would be the perfect day to find a nice place in the bar and work on resolving the open issues in Innotop to support MariaDB 10.1, MySQL 5.7…
If you are interested just send me a tweet (@lefred) and we can arrange this meeting.
GUI monitoring tools for MySQL are not always suitable for all our needs or situations. Most of them are designed to provide historical views into what happens to our database over time rather then real-time insight into current MySQL server status. Excellent free tools for this include Cacti, Zabbix, Ganglia, Nagios, etc. But each of them needs to be properly configured to provide details on what is going on in our MySQL instances. And setting up one of these monitoring solutions is neither quick nor trivial (well, maybe with the exception of Ganglia).
MySQL Workbench provides …
[Read more]
Lefred and I spent a bit of time
making innotop 1.9.1.
We’ve released a new version mainly to include MySQL 5.6 support
as well as including some bugs fixed by Baron Schwartz
and Frédéric Descamps.
You can download the .tar.gz and rpm’s (new!) at
http://code.google.com/p/innotop/downloads/list
Bugs fixed:
Percona Server for MySQL version 5.1.68-14.6
Percona is glad to announce the release of Percona Server 5.1.68 -14.6 on April 19, 2013 (downloads are available here and from the Percona Software Repositories). Based on MySQL 5.1.68, including all the bug fixes in it, Percona Server 5.1.68-14.6, a MySQL alternative, is now the current stable release in the 5.1 series. All …
[Read more]I’ve just released innotop version 1.9.0. This version fixes a lot of bugs, makes the tool work better when monitoring dozens of MySQL servers, and adds two new modes: a Health Dashboard and an InnoDB Blockers/Blocked mode.
Further Reading:
I’m using innotop again every day, for the first time in a few years. I found that I didn’t like the tool that the younger and less experienced version of me created. It is very flexible and has the ability to surface a lot of information about MySQL, but not all on one screen. I wanted a “single pane of glass” health dashboard for the servers I’m monitoring, instead of having to look on various screens for important bits of information.
The good news is, innotop is very extensible and I know the code because I wrote most of it, so in a short while I had a dashboard that suited me. I committed these changes to trunk, so if you wish you can easily get the code:
$ wget innotop.googlecode.com/svn/trunk/innotop
$ chmod +x innotop
$ ./innotop
You can select the new ‘A’ mode by pressing the capital ‘A’ key. Here is a screenshot (click for full size version):
…
[Read more]The new stable version of innotop is now released. Version 1.8.1 is a bug-fix-only release, with no new features. It’s available for immediate download.
Further Reading:
First of all, I wish you a happy new
year.
Many things happened last year, it was really exciting to be
involved in the MySQL ecosystem.
I hope this enthusiasm will be increased this year, up to you !
To start the year, I propose the MySQL[plus] Awards
2011
It will only take 5 minutes to fill out these
polls.
Answer with your heart first and then with your experience with
some of these tools or services.
Polls will be closed January 31, so, vote now
!
For “other” answers, please, let me a comment with
details.
Don’t hesitate to submit proposal for tools or services in the
comments.
And, please, share these polls !
Note: There is a poll embedded within this post, …
[Read more]A customer opened a support issue to ask about some help determining why they were seeing a lot of Lock Wait Timeouts. I asked them to enable the InnoDB Lock Monitor so that I could get a look at what was going on in their transactions and whether there might be some locks held longer than necessary.
The customer sent in a 184MB MySQL error log with 4773836 lines. I started looking through it, but I could tell I was going to need a better way to get a better overview of the file than what I'd be able to piece together trying to poke through it and look for individual lines. I started piping the file through a variety of UNIX tools to narrow down what I was seeing.
I ended up with this mess:
< mysqld.err grep ACTIVE | cut -d' ' -f 2,4 | sort -rn -k 2 | perl -F, -ane 'print "$F[0] $F[1]" if not $v{$F[0]}; $v{$F[0]} = $F[1];' | head
It's hideous, but it's pretty helpful. Here's the output:
1EC080F1 …[Read more]