This is a discussion on MySQL Cluster within the Database Support forums, part of the Web Development category; MySQL Cluster is a technology that enables clustering of in-memory databases in a shared-nothing system. The shared-nothing ...
| |||||||
| Register | FAQ | Members List | Calendar | Mark Forums Read |
| |||
| MySQL Cluster is a technology that enables clustering of in-memory databases in a shared-nothing system. The shared-nothing architecture allows the system to work with very inexpensive hardware, and with a minimum of specific requirements for hardware or software. MySQL Cluster is designed not to have any single point of failure. For this reason, each component is expected to have its own memory and disk, and the use of shared storage mechanisms such as network shares, network filesystems, and SANs is not recommended or supported. MySQL Cluster integrates the standard MySQL server with an in-memory clustered storage engine called NDB. In our documentation, the term NDB refers to the part of the setup that is specific to the storage engine, whereas “MySQL Cluster” refers to the combination of MySQL and the NDB storage engine. A MySQL Cluster consists of a set of computers, each running a one or more processes which may include a MySQL server, a data node, a management server, and (possibly) a specialized data access programs. The relationship of these components in a cluster is shown in the attached image All these programs work together to form a MySQL Cluster. When data is stored in the NDB Cluster storage engine, the tables are stored in the data nodes. Such tables are directly accessible from all other MySQL servers in the cluster. Thus, in a payroll application storing data in a cluster, if one application updates the salary of an employee, all other MySQL servers that query this data can see this change immediately. The data stored in the data nodes for MySQL Cluster can be mirrored; the cluster can handle failures of individual data nodes with no other impact than that a small number of transactions are aborted due to losing the transaction state. Because transactional applications are expected to handle transaction failure, this should not be a source of problems. For further details MySQL AB :: MySQL 5.0 Reference Manual :: 15.1 MySQL Cluster Overview
__________________ With, J. Jeyaseelan Everything Possible |
| Sponsored Links |
![]() |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Row order in cluster & non-cluster index? | prasath | Database Support | 1 | 08-08-2007 12:35 AM |
| What is a table called, if it does not have neither Cluster nor Non-cluster Index?.. | Archer | Database Support | 2 | 07-19-2007 12:19 AM |
| Cluster & Non cluster index | prasath | Database Support | 1 | 07-16-2007 05:29 AM |
| Oracle Cluster - Create and Alter Basic Syntax | Murali | Database Support | 2 | 07-11-2007 06:40 AM |
| cluster index in Oracle | vigneshgets | Database Support | 1 | 07-10-2007 07:22 AM |