MySQL Cluster: Difference between revisions

Revision as of 05:01, 9 December 2018

Revision as of 18:18, 27 January 2019

Line 1:

{{Short description|Auto-sharding technology for MySQL databases}}

{{Use mdy dates|date=January 2019}}

{{Use American English|date=January 2019}}

{{primary sources|date=December 2012}}

{{Infobox software

| name = MySQL Cluster

| title =

| logo =

| logo size = 180px

| logo caption =

| screenshot = <!-- [[File: ]] -->

| caption =

| collapsible =

| author =

| developer = [[Oracle Corporation|Oracle]]

| released = November 2004

| discontinued =

| latest release version = 7.6

| latest release date = {{Start date and age|2018|06|01}} <ref>https://blogs.oracle.com/mysql/mysql-cluster-76-is-now-generally-available</ref> <!-- {{Start date and age|YYYY|MM|DD|df=yes/no}} -->

| operating system = [[Cross-platform]]{{which?|date=January 2019}}

| latest preview version =

| latest preview date = <!-- {{Start date and age|YYYY|MM|DD|df=yes/no}} -->

| frequently updated = <!-- DO NOT include this parameter unless you know what it does -->

| programming language =

| operating system = [[Cross-platform]]

| platform =

| size =

| language = English

| status =

| genre = [[Relational database management system|RDBMS]]

| license = [[GNU General Public License]] (version 2, with [[GPL linking exception|linking exception]]) or commercial [[EULA]]

| alexa =

| website = <ref>[http://www.mysql.com/products/cluster/ Cluster CGE]. MySQL. Retrieved on 2013-09-18.</ref>

}}

Line 35 ⟶ 22:

===Replication===

Internally MySQL Cluster uses [[synchronous replication]] through a [[two-phase commit]] mechanism in order to guarantee that data is written to multiple nodes upon committing the data. (This is in contrast to what is usually referred to as "MySQL Replication", which is [[wikt:asynchronous{{linktext|asynchronous]]}}.) Two copies (known as ''replicas'') of the data are required to guarantee availability. MySQL Cluster automatically creates “node groups” from the number of replicas and data nodes specified by the user. Updates are synchronously replicated between members of the node group to protect against data loss and support fast failover between nodes.

It is also possible to replicate asynchronously between clusters; this is sometimes referred to as "MySQL Cluster Replication" or "geographical replication". This is typically used to replicate clusters between data centers for [[disaster recovery]] or to reduce the effects of network latency by locating data physically closer to a set of users. Unlike standard MySQL replication, MySQL Cluster's geographic replication uses [[optimistic concurrency control]] and the concept of Epochs to provide a mechanism for conflict detection and resolution,<ref>[http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-replication-conflict-resolution.html MySQL :: MySQL 5.6 Reference Manual :: 17.6.11 MySQL Cluster Replication Conflict Resolution]. Dev.mysql.com. Retrieved on 2013-09-18.</ref> enabling active/active clustering between data centers.