Hi all, keeping our steady release cycle, it is time again to do another preview release of MySQL Group Replication, the plugin that brings multi-master update everywhere to MySQL, like we described in Hello World post.
We are very proud to do the fourth preview release of MySQL Group Replication, version 0.5.0 based on MySQL Server 5.7.8, which introduces new exciting features, please enjoy the highlights!…
One of the key features of MySQL Group Replication is its distributed recovery mechanism. Whenever a new member joins a server group, making use of this plugin component, it reaches to a suitable donor and fetches the data that it misses up until the point it is declared online.…
Today, at the Strata Conference in Santa Clara, Calpont Corporation announced that it is changing its name to InfiniDB, Inc., and that it has raised another $7.5M in funding. So “What’s in a name?” you ask? For InfiniDB, a lot, actually. Since its introduction in 2010, the InfiniDB database has delivered exceptional scaling and speed, […]
In 0.5.0 version of MySQL Group Replication plugin, we have introduced the Auto-increment configuration/handling feature through which auto increment variables (auto_increment_increment and auto_increment_offset) are auto configured by the plugin, so that different members of the group don’t generate duplicated auto increment values.…
In this post, we will describe the Primary Component, a central concept in how Galera ensures that there is no opportunity for database inconsistency or divergence between the nodes in case of a network split.
What is the Primary Component?
The Primary Component is that set of Galera nodes that can communicate with each other over the network and contains the majority of the nodes. In case of a network partition, it is those nodes that can safely commit a transaction. A cluster can only have one such set of nodes, as there can only be one majority. No other set of nodes will commit transactions, thus removing the possibility of two parts of the cluster committing different transactions and thus diverging and becoming inconsistent.
The Healthy Cluster
In a healthy cluster, all nodes nodes can communicate with each other, so they all belong to the Primary Component and can all receive updates. There are no …
[Read more]Hi all, it is time again to do another preview release of MySQL Group Replication, the plugin that brings multi-master update everywhere to MySQL, like we described in Hello World post.
We are very proud to do the third preview release of MySQL Group Replication, which introduces new exciting features, please enjoy the highlights!…
Here is version 0.4.0 of the MySQL Group Replication plugin, our solution that gives you virtual synchronous updates on any member of a MySQL server group. With this new version you can expect a bunch of bug fixes and new features.…
The multi master plugin for MySQL is here. MySQL Group Replication provides virtually synchronous updates on any member in a group of MySQL servers, with conflict handling and automatic group membership management and failure detection.
You can read about all MySQL Group Replication features following the tag MySQL Group Replication.
On this blog post we will present the packages the MySQL Group Replication 0.4.0 offers and what are the tasks that you need to perform to install the plugin on the MySQL server.
Packages
Go to http://labs.mysql.com/, choose MySQL Group Replication on the release menu. You will see two files there:
As we are collecting an ever increasing amount of data and analyzing it, data storage products with alternate file structures have become popular, such as LSMs (log structured merge files) which is implemented in Cassandra and Hbase, as well as fractal indexes found in TokuDB/MX, which is an alternate file structure plugin for mysql and [...]
It mentions in the message that you can try to repair it. Also, if you look at the actual FILEPATH you get, you can find out more:
/tmp/#sql_actor_return it means that MySQL
needs to create a temporary table because of the query size. It
stores it in /tmp, and that there is not enough space in your
/tmp for that temporary table. increase the tmp_table_size
variable and /tmp/ partition size