As a developer of an application there really isn't a problem better than finding that you have to scale up the application and the database that supports it to handle the increased load. The main bottleneck to most expansion is the database server and in many modern environments that replication is based around MySQL.
Application servers are easy to add on to the front-end of your environment.
The -N or –skip-column-names is a convenient option with the
mysql client to skip the header line of output.
However I found when viewing the output via the terminal, some
interesting and unexplained output.
$ mysql -h*** -u*** -p -e "SELECT VARIABLE_NAME,VARIABLE_VALUE FROM INFORMATION_SCHEMA.GLOBAL_STATUS" +--------------------------------+----------------+ | VARIABLE_NAME | VARIABLE_VALUE | +--------------------------------+----------------+ | ABORTED_CLIENTS | 710001 | | ABORTED_CONNECTS | 31 | | BINLOG_CACHE_DISK_USE | 0 | | BINLOG_CACHE_USE | 0 | | BYTES_RECEIVED | 2522301004 | | BYTES_SENT | 317785976 | | COM_ADMIN_COMMANDS | 2890667 | | COM_ASSIGN_TO_KEYCACHE | 0 | | COM_ALTER_DB | 0 | | COM_ALTER_DB_UPGRADE | …[Read more]
On Wednesday night, the Boston MongoDB User group was kind enough to have me speak about TokuMX Internals. I spoke about Fractal Tree® indexes and the technical reasons behind the benefits they provide to MongoDB applications. Although the talk mostly references TokuMX and MongoDB, all the theory applies to TokuDB and MySQL as well.
My slides are on our technology overview page, along with other great content.
Opportunities to present technical material to an engaged audience asking tough questions is rare, and much appreciated. So thank you to the Boston MongoDB User group for having …
[Read more]” One of the biggest challenges with any project of such a long duration is coping with change. There are many aspects to coping with change, including changes in requirements, changes in technology, vendor stability, changes in staffing and so on”–Jon Brumfitt. On May 14, 2009, the European Space Agency launched an Arianne 5 rocket [...]
Thanks to all who attended my “MySQL Query Tuning” webinar on July 24. If you missed it, you can you can download the slides and also watch the recorded video. Thank you for the excellent questions after the webinar as well. Query tuning is a big topic and, due to the limited time, I had to skip some material, especially some of the monitoring. I would like, however, to answer all the questions I did not get into during the webinar session.
Q: Did you reset the query cache before doing your benchmark on your query? 0.00 seconds sounds too good
A: (This is in response to a …
[Read more]The MySQL Developer Tools team is pleased to announce the availability of MySQL Workbench 6.0.5 Release Candidate. MySQL Workbench 6.0 is the new major update of the Development and Administration tool for MySQL. This release includes over 200 bug fixes and implemented enhancement requests, 30 new features and a new redesigned UI. As a development version, this release is not suitable for production use. Please test and file your bug reports at http://bugs.mysql.com
As always, MySQL Workbench is natively available on Windows, Mac, Linux.
Improvements in MySQL Workbench 6.0:
In this webinar, recorded 7/31/13, Wiqar Chaudry (Tech Evangelist at NuoDB) demonstrates how to easily replicate from MySQL to NuoDB with Tungsten Replicator.
In addition, see Philip Stoev's blog describing how to configure replication between MySQL and NuoDB using Tungsten Replicator.
Idle connections can cause problems both at the application side, increasing the risk of connection timeouts for applications where persistent connections are used, and the server side, where resources remain allocated to idle connections. Any application with persistent connections, such as a JDBC application using a connection pool, will have periods where connections are idle – but it’s good to know how much time is spent idle. Too much idle time might mean connections pools configured to allow too many connections to sit idle in a connection pool, or not properly doing connection pool maintenance.
PERFORMANCE_SCHEMA in MySQL 5.6 makes it trivial to measure
absolute time spent waiting. This will show total, average
and maximum idle times by account:
mysql> SELECT …[Read more]
Installed on a clean CentOS 6.4 AWS instance.
sudo su - cd /tmp wget http://cdn.mysql.com/Downloads/MySQL-5.6/MySQL-5.6.13-1.el6.x86_64.rpm-bundle.tar tar xvf MySQL-5.6.13-1.el6.x86_64.rpm-bundle.tar yum install -y libaio perl rpm -i MySQL*.rpm
The following output is the sign that security is being considered with new MySQL versions. Woot!
A RANDOM PASSWORD HAS BEEN SET FOR THE MySQL root USER ! You will find that password in '/root/.mysql_secret'. You must change that password on your first connect, no other statement but 'SET PASSWORD' will be accepted. See the manual for the semantics of the 'password expired' flag. Also, the account for the anonymous user has been removed. In addition, you can run: /usr/bin/mysql_secure_installation which will also give you the option of removing the test database. This is strongly recommended for production servers. See the manual for more instructions. Please report any problems with the …[Read more]
This is MySQL's Bad Idea #573 (after #384, which I've blogged about before) I've just had a terrible experience with a bug report from the jOOQ User Group, related to escaping of backslashes in string literals in MySQL. First, I thought to myself, whatever. SQL doesn't escape backslashes. The only escape character within a string … Continue reading MySQL Bad Idea #573 →