The MariaDB Foundation is pleased to announce the immediate availability of MariaDB 5.5.60. This is a stable (GA) release. See the release notes and changelog for details. Download MariaDB 5.5.60 Release Notes Changelog What is MariaDB 5.5? MariaDB APT and YUM Repository Configuration Generator Contributors to MariaDB 5.5.60 Alexander Barkov (MariaDB Corporation) Alexey Botchkov (MariaDB […]
The post MariaDB 5.5.60 now available appeared first on MariaDB.org.
Introduction
In this post we will explore one approach to MySQL high
availability with HAProxy, Consul and Orchestrator.
Let’s briefly go over each piece of the puzzle first:
– HAProxy is usually installed on the application servers or an
intermediate connection layer, and is in charge of connecting the
application to the appropriate backend (reader or writer). The
most common deployment I’ve seen is to have separate ports for
writes (which are routed to the master) and reads (which are load
balanced over a pool of slaves).
– Orchestrator’s role is to monitor the topology and perform auto
recovery as needed.
The key piece here is how we can make HAProxy aware that a
topology change has happened, and the answer lies within Consul
(and Consul templates).
– Consul is meant to be told the identity of the new master by
Orchestrator. By leveraging Consul templates, we can then in turn
propagate that …
The MySQL Development Team is proud to announce the second GA release of InnoDB cluster!
We listened carefully to the feedback we got from the previous major release (1.0 GA) and the last release candidate (8.0.4 RC) and incorporated many of the suggested changes.…
The MySQL Development Team is proud and happy to announce the General Availability release of InnoDB Cluster 8.0! This is an extremely exciting release of our integrated, native, full stack High Availability (HA) solution for MySQL.
InnoDB Cluster provides an out-of-the-box and easy to use built-in HA and Scaling solution for MySQL by tightly integrating the following GA components:
…
Yesterday I was presenting on the MySQL Document Store and was
asked if the _id fields created by the server as an InnoDB
primary key is a UUID. I knew that it was not a UUID but I
had to hit the documentations
(https://dev.mysql.com/doc/x-devapi-userguide/en/understanding-automatic-document-ids.html)
to find out what the document ID really is -- a very interesting
piece of information.
The Details If you are inserting a document lacking a
_id key, the server generates a value. The _id is
32 bits of a unique prefix (4 bytes), a time stamp (8 bytes), and
serial number (16 bytes). The prefix is assigned by the InnoDB
Cluster to help ensure uniqueness across a cluster. The timestamp
is the encoded startup time of the server. The serial
numbers uses the auto increment offset and auto
increment increment server variables . From the manual
page:
This document ID format ensures …
When maintainng any piece of software, we usually deal with two kind of actions:
bugs and features
A bug happens when there is an error in the software, which does not behave according to the documentation or the specifications. In short, it's a breech of contract between the software maintainer and the users. The promise, i.e. the software API that was published at every major version, is broken, and the software must be reconciled with the expectations and fixed, so that it behaves again as the documentation says. When we fix a bug in this way, we increment the revision number of the software version …
[Read more]It’s hard to believe Percona Live 2018 starts on Monday! We’re looking forward to seeing everyone in Santa Clara next week! Here are some quick highlights to remember:
Restore requests are common and so are the restores of specific
entities: a database, or one or more table(s). This has been
discussed a lot and we have plenty of tools and solutions already
available.
In this blog post we will cover an interesting solution that I
came across when I received a restoration request from a client
with a specific scenario.
The scenario? Well, the client was on a Windows server with 400GB of mysqldump and wanted to restore a table.
As Linux players we already know of some tools and techniques to export a table or database from mysqldump – for example, using sed command or using the script mysqldumpsplitter (based on sed itself). But on Windows we are powerless by not being able to use sed (we’re sad without sed.) Also, there was no cygwin to ease up the pain.
We had to come-up with a solution that works on …
[Read more]Percona announces the release of Percona Toolkit 3.0.9 on April 20, 2018.
Percona Toolkit is a collection of advanced open source command-line tools, developed and used by the Percona technical staff, that are engineered to perform a variety of MySQL®, MongoDB® and system tasks that are too difficult or complex to perform manually. With over 1,000,000 downloads, Percona Toolkit supports Percona Server for MySQL, MySQL, MariaDB®, Percona Server for MongoDB and MongoDB.
Percona Toolkit, like all Percona software, is free and open source. You can download packages from the website or install from official repositories.
This …
[Read more]Percona Monitoring and Management (PMM) is a free and open-source platform for managing and monitoring MySQL® and MongoDB® performance. You can run PMM in your own environment for maximum security and reliability. It provides thorough time-based analysis for MySQL® and MongoDB® servers to ensure that your data works as efficiently as possible.
We focused mainly on two features in 1.10.0, but there are also several notable improvements worth highlighting:
