5

We want to setup a mysql cluster with master-master sync replication, to provide HA so that one db for write from one app, other for write from other app. It is a webapp with high write and medium read

We are considering adding mysql cluster and considering percona vs mysql cluster.

Can MySQL ndb cluster import innodb dump ?

Can ndb cluster support MySQL async and 2-way sync replication ?

Can ndb guarantee consistency since it does not write to disk? I.e. What if there is 2 node cluster and both go down and data is not flushed to disk

can ndb cluster support 4-5 table join, ? Will the tables be in same node or will there be any network latency due to distributed joins

Does ndb cluster support MySQL-fabric Python api ?

Does ndb cluster support multi-master bi-directional sync?

Does percona cluster support above items ?

|improve this question

closed as primarily opinion-based by Philᵀᴹ, Paul White♦, Vérace, Colin 't Hart, Michael Green Mar 20 '15 at 11:04

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

  • AIUI, MySQL Cluster is an In-Memory based system, whereas Percona/MariaDB systems are disk based. – Vérace Mar 19 '15 at 22:55
  • 1
    Not anymore. Or, at least the NDB Cluster data can be on disk now. – Rick James Mar 21 '15 at 1:21
  • Why question is still on hold? – doesnt_matter Mar 22 '15 at 3:12
  • 1
    3 people have voted to reopen. 2 more votes are needed. – ypercubeᵀᴹ Mar 23 '15 at 14:44
  • 3
    We had exact same issues in production every day. We spend months trying to figure out correct answers. All these moderators are a bunch of babies, give nerds a little bit of power and it goes str8 to their heads. 'opinion based' my a.. – doesnt_matter Jun 8 '16 at 0:04
0

It's hard to say which is "better" -- Percona's PXC or MariaDB w/Galera. Both use Galera as the underlying "cluster" technology and HA. Percona is based on Oracle's 5.6, MariaDB is slightly forked back around 5.5 timeframe. But both are great.

In any case, you really need 3 servers to get HA. The 3rd is the tie-breaker in case one goes down.

Furthermore, if HA is a big priority, the think about tornadoes, earthquakes, floods, etc. The 3 machines should not be in the same geographic location.

Bottom line: Flip a coin for picking between them. (I'm eager to hear from those who have a strong bias, but if you do, please state whether you have ties to one or the other.)

Don't use NDB Cluster -- it is too far from the main path of things. There is a lot of setup required, and it has a bunch of limitations.

|improve this answer
  • Thanks, But It appears that mysql-cluster in ndb storage engine and we are usign innodb. also it keeps some data in-memory with periodic flush to disk. ? is this a good choice for our innodb app? Also it seems it can handle only simple queries. That is why we are leaning toward Percona/Mariadb – doesnt_matter Mar 19 '15 at 21:52

Not the answer you're looking for? Browse other questions tagged or ask your own question.