This past week was marked by a series of personal findings related to the use of Global Transaction IDs (GTIDs) on Galera-based clusters such as Percona XtraDB Cluster (PXC). The main one being the fact that transactions touching MyISAM tables (and FLUSH PRIVILEGES!) issued on a giving node of the cluster are recorded on a GTID set bearing the node’s server_uuid as “source id” and added to the binary log (if the node has binlog enabled), thus being replicated to any async replicas connected to it. However, they won’t be replicated across the cluster (that is, all of this is by design, if wsrep_replicate_myisam is …
[Read more]
Hej alla SMUG:are!
Nu är det återigen dags för en ny träff, och detta är ju lagom i
tiden för att prata lite om kommande 5.7-releasen.
Vi kommer att bjudas på två presentationer denna gången, en som
hålls av Mattias Jonsson, utvecklare i InnoDB teamet, om
partionering i 5.7. Här finns det många nyheter, ni kan kolla
lite på server teamets blog,
http://mysqlserverteam.com/category/partitioning/
Den andra presentationen hålls av Martin Hansson, utvecklare i
MySQL server teamet. Ämnet är den nya kostnadsmodellen för
planering av frågor i MySQL 5.7, detta är också en stor ändring
som kommer i 5.7. Läs lite mer här:
http://mysqlserverteam.com/optimizer-cost-model-improvements-in-mysql-5-7-5-dmr/
Denna gången är det King som bjuder på lokaler och lite käk, så
om ni går runt med candy crush på telefonen så känns det säkert
som hemma!, så stort tack till King!
…
VMware Continuent, a multi-site, multi-master database cluster solution, provides a full data management solution that is already handling billions of transactions daily for our customers, on-premises and in the cloud. Join us to learn how Continuent and MySQL can run business-critical applications in vCloud Air, VMware's hybrid cloud solution.
In this new webinar-on-demand, you will learn
MySQL’s default storage engine as of version 5.5 is InnoDB. InnoDB maintains a storage area called the buffer pool for caching data and indexes in memory. By keeping the frequently-accessed data in memory, related searches are retrieved much faster than reading from disk.
When you stop or restart MySQL, you lose the cached data stored in the buffer pool. There is a feature in MySQL 5.6 which allows you to dump the contents of the buffer pool before you shutdown the mysqld process. Then, when you start mysqld again, you can reload the contents of the buffer pool back into memory. You may also …
[Read more]
There are generally three components to any benchmark
project:
- Create the benchmark application
- Execute it
- Publish your results
I assume many people think they want to run more benchmarks but
give up since step 2 is extremely consuming as you expand the
number of different configurations/scenarios.
I'm hoping that this blog post will encourage more people to
dive-in and participate, as I'll be sharing the bash script I
used to test the various compression options coming in the MongoDB
3.0 storage engines. It enabled me to run a few different
tests against 8 different configurations, recording insertion
speed and size-on-disk for each one.
If you're into this sort of thing, please read on and provide any
feedback or improvements you can think of. …
When we launched repos for SUSE Linux 11 back in December, we said we would be adding SUSE 12 support as soon as possible, and we are happy to announce that as of last week the repo offers MySQL Server packages for SUSE 12. It did take us a little bit of extra time to get this […]
In a previous post, titled “Multi-threaded replication with MySQL 5.6: Use GTIDs,” I explained that using GTID replication is almost a requirement when using MySQL 5.6 MTS. Let’s see now how to perform the day-to-day operations when MTS and GTIDs are both enabled. (I’ll also be presenting a related webinar next week titled “Multi-threaded Replication in MySQL 5.6 and 5.7″).
Seeing the execution gaps
If you have a look at SHOW SLAVE STATUS
while the
slave is running, you may not be expecting such an output:
[...] Executed_Gtid_Set: …[Read more]
On Wednesday, February 25 at 18:00 CET (9 am Pacific Time), I
will do webinar on how to analyze and tune MySQL queries for
better performance.
The webinar covers how the MySQL optimizer chooses a specific
plan to execute SQL queries. I will also show you how to use
tools such as EXPLAIN (including the new JSON-based output) and
Optimizer Trace to analyze query plans. We will also review how
the Visual Explain functionality available in MySQL Workbench
helps us visualize these plans. The webinar will also contain
several examples of how to take advantage of the query analysis
to improve performance of MySQL queries.
The presentation will be approximately 60 minutes long followed
by Q&A.
For details on how to register for the webinar
visit …
Thanks Mark, this makes it so much easier!
Hi Keith,
Thanks for blogging about MEM and the bulk add feature. I thought you might like to know, that for an environment like yours, there’s an even *easier* way to configure this. MySQL Enterprise Monitor also has an “automatically monitor after process discovery” feature that works as long as you have credentials that are the same on all of your instances (which in your case, they are). Go to Configuration -> Advisors, then open the “Monitoring and Support Services” category, and expand it. Click on the drop-down menu for the “MySQL Process Discovery” entry, and choose “Edit Advisor Configuration”. Answer “Yes” for the “Attempt Connection” choice, and the rest is similar to the add/edit connection dialog. Once this is configured, any time a MEM agent discovers a MySQL process that MEM isn’t monitoring, it will first attempt to use this stored set of credentials to setup monitoring of that instance.