Automatic Database Sharding with MySQL Cluster

MySQL Cluster automatically shards at the database layer, spreading the database out across nodes so that developers do not have to write complex and intrusive application-sharding logic (which is required by other platforms).

To understand the types of nodes in a MySQL Cluster and to learn how to design, install, configure, and maintain this product, take the MySQL Cluster training course. Below is a selection of the events already on the schedule for this 3-day training course:

 Location  Date  Delivery Language
Sao Paolo, Brazil
28 July 2014 Brazilian Portuguese
Berlin, Germany
11 August 2014 German
Hamburg, Germany
29 September 2014 German
Munich, Germany
16 July 2014 German
Seoul, Korea
23 June 2014 Korean
Petaling Jaya, Malaysia
16 July 2014 English
Warsaw, Poland
4 June 2014 Polish
San Francisco, CA, United States
28 May 2014 English

To register for an event, request an additional event or learn more about the authentic MySQL curriculum, go to http://education.oracle.com/mysql.

Comments:

wanted to ask 1 question. i have not been able to get this doubt cleared.

1) max no of data nodes in cluster
2) max. data set size per node.

if you could help me out with this, that would be great.

Posted by guest on May 19, 2014 at 12:16 PM GMT #

The upper limit of data nodes is 48.
There is no practical upper limit on the amount of data on a data node, since you store most of the data in memory and some of it on the disk. The amount of data you can store on a node is affected by your memory configuration.
For example, a 48-node MySQL Cluster with 512 GB RAM per node has a total of 24 TB RAM, which provides a typical in-memory working data size of under 12TB total with two nodes per node group.
http://mysql.com/why-mysql/white-papers/mysql_cluster_eval_guide.php contains some calculations that help determine the approximate memory sizing requirements for data nodes.

Posted by guest on May 19, 2014 at 07:33 PM GMT #

hi thank you so much for the information.

is there any limit to data set size per node on disk ?

Posted by guest on May 20, 2014 at 03:31 AM GMT #

Regarding the limit of data set size per node on disk, I draw your attention to information in the MySQL documentation. For example you can see information on disk data here: http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-limitations-disk-data.html and http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-limitations-database-objects.html. You can read that the maximum number of all NDB database objects in a single MySQL Cluster-including databases, tables and indexes-is limited to 20320; A MySQL Cluster Disk Data table can use at most 1 tablespace and the theoretical upper limit to the amount of data (in bytes) that can be stored on a disk by a single NDB table is approximately 2 petabytes. This leads to a maximum theoretical disk data size per data node of almost 40 exabytes, depending on the data distribution between tables.

Posted by Antoinette O'Sullivan on May 20, 2014 at 08:38 AM GMT #

Post a Comment:
Comments are closed for this entry.
About

Get the latest updates on products, technology, news, events, webcasts, customers and more.

Twitter


Facebook

Search

Archives
« July 2015
SunMonTueWedThuFriSat
   
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
 
       
Today