Geek Answers Handbook

MySQL Cluster Issues

I read most of the MySQL cluster docs and some tutorials, but I still have some obscure things, and the main ones right now:

  • When the node data reloads (crashes and goes up again), will the data be available? Will updates / additions work as usual? Will it “sync”?
  • Does a cluster work faster than a standalone one? In particular, I update the lines many times, but one at a time, which means that network latency can affect performance. Is there any pattern that I can track to speed things up, like adding more SQL nodes or adding mode data nodes?

As for question number 2, updating the line has the following syntax:

UPDATE db_accounts.tbl_items SET items=items+%lld WHERE id_account=%u

"id_account" is an index (unique).

+5
source share
2 answers

MySQL Cluster is a database in memory (although some columns can be stored on disk, indexed columns cannot). If the plug pulls, your data will disappear. The recovery process for a node to re-cluster the cluster is that it extracts the data that it has lost from the surviving node (requiring good fast connections between nodes), and then carefully applies replication events until it catches up and can actively participate . If the last backup is available, you can rebuild it from it instead of another node, but the principle is the same: node must be populated with data from scratch.

MySQL Cluster - -. NDB node, , , . , , . , - .. - .

, , , , .

+8

MySQL Cluster , ( ).

( ), . , , , , .

node , , , - node.

, MySQL ( , ).

+5

More articles:


All Articles