In this post we will use the MySQL 5.7.7 labs release which has support for JSON documents stored in a special data type. We will be using Connector/Python and show how to get going with updating documents and getting data out.
Required read
If you wonder what this is all about, please check the following great reads from the MySQL Server team:
mydumper is a a tool for fast reliable logical backups. It is an alternative to mysqldump and has many advantages over mysqldump some of which are listed below:
MySQL recently added support for JSON data with MySQL 5.7.8. It would be cool to store
JSON data in TokuDB tables.
First, I had to get TokuDB running on MySQL 5.7.8. TokuDB currently runs on
Percona Server 5.6, and various flavors of MariaDB. The
only issues porting TokuDB to MySQL 5.7 were adopting the
changes to various internal APIs that storage engines use.
Since I did not make any patches to the MySQL code,
some TokuDB features including clustered secondary keys and
selection of various compression algorithms …
When a new version of MySQL is about to be released we read a lot of blog posts about the performance and scalability improvements. That’s good but sometimes we miss some small features that can help us a lot in our day-to-day tasks. One good example is the blog post that Aurimas wrote about a new small feature in MySQL 5.6 that I didn’t know about until I read it: the Automatic InnoDB transaction log file size change. How cool is that?
I plan to write a series of blog posts that will show some of those small new features in MySQL 5.7 that are going to be really useful. I’m going to start with EXPLAIN FOR CONNECTION.
This feature allows us to run an EXPLAIN for an already running statement. Let’s say that you find a query …
[Read more]http://mysqlserverteam.com/removal-and-deprecation-in-mysql-5-7/
A useful overview of options, syntax and tools that have been deprecated or removed for the upcoming MySQL 5.7 release.
Backup and restore is one of the most important aspects of database administration. If a database crashed and there was no way to recover it, any resulting data loss might lead to devastating results to a business. As the DBA operating a MySQL or Galera cluster in production, you need to ensure your backups are scheduled, executed and regularly tested.
There are multiple ways to take backups, but which method fits your specific needs? How do I implement point in time recovery?
Join us for this live session on backup strategies for MySQL and Galera clusters led by Krzysztof Książek, Senior Support Engineer at Severalnines.
DATE & TIME
Europe/MEA/APAC
Tuesday, June 30th at 09:00 BST / 10:00 CEST (Germany, France,
Sweden)
Register Now
North America/LatAm …
[Read more]In a post, written a few months ago, I found that using EXT4 transactions with the “data=journal” mount option, improves the write performance significantly, by 55%, without putting data at risk. Many people commented on the post mentioning they were not able to reproduce the results and thus, I decided to further investigate in order to find out why my results were different.
So, I ran sysbench benchmarks on a few servers and found when the InnoDB double-write buffer limitations occur and when they don’t. I also made sure some of my colleagues were able to reproduce the results. Basically, in order to reproduce the results you need the following conditions:
With the shipment of the first release candidate (RC) of MySQL 5.7, the next major version of the server is rapidly shaping up. Over the course of the nearly two and a half years that have passed since 5.6 went GA, we have put a lot of work into streamlining the server code in order to ease the burden of developing and maintaining such a large product and codebase.
An important aspect of this work is deprecation and removal. To explain the terms, deprecating a feature means that we signal to the outside world that “this feature is available now, but it will be removed in a future release, so please adjust your use case accordingly”. Removing a feature means just that – in one version the feature is available, but then it is gone, and if you try to use it, you will get an error message saying that the feature is unknown.
Generally we don’t remove features in existing GA releases, but we …
[Read more]Some applications, particularly those written with a single-node database server in mind, attempt to immediately read a value they have just inserted into the database, without making those those operations part of a single transaction. A read/write splitting proxy or a connection pool combined with a load-balancer can direct each operation to a different database node.
Since Galera allows, for performance reasons, a very small amount of “slave lag”, the node that is processing the read may have not yet applied the write. It can return old data, causing an application that did not expect that to misbehave or produce an error.
The Solution
Through the mechanism of flow control, slave lag is kept to a minimum, but additionally Galera provides the causal wait facility for those queries that must always see the most up-to-date …
[Read more]If you draw a diagram of information flow and interaction amongst teams and processes in IT, you’ll probably find that although some parts of the organization are “leaf” or “edge” nodes, the people who manage the data are not. The DBAs would usually be one of the lavender circles in the chart below, not a blue circle.
DBAs also occupy a central position in the continuum of skills:
• On one hand, they have to understand a lot about how the application code works, because application developers are their customers.
• On the other hand, they need to understand how the application runs in production, because operations staff are also their customers.
DBAs end up knowing a lot about everything, and because they can develop this all-encompassing set of skills and knowledge, the organization relies on them to do so.
Consider the old adage, “if you want to get something done, ask a busy …
[Read more]