Hi, Is it possible with ArangoDB 3 to set up such a cluster environment (i.e. with automatic failover and rebalancing) without having to rely on mesos? In other words, how tight is the coupling of ArangoDB 3 and mesos?
The reason I'm asking this is that we are currently considering other orchestration frameworks such as swarm or k8s. Bart On Friday, April 1, 2016 at 12:40:51 PM UTC+2, Claudius Weinberger wrote: > > > > Sébastien Médan schrieb: > > I have a few questions regarding the choice of ArangoDB to offer > persistence in our cloud components. > > How well does ADB scale when adding nodes to cope with increasing loads: > Can the `numberOfShards` attribute be altered on existing collections? > > Altering the numOfShards is not possible at the moment. It will come later > this year. Nevertheless, that will be an expensive operation. But you can > choose a numOfShards value easily by factor 100 of your current number of > servers so that you can grow your cluster up to this size. You need at > least one shard per machine. To take a numOfShards by factor 100 will not > have a notable performance implication. > > Can we rebalance (even manually) after adding a node? > > At the moment this a manual process with, unfortunately, a downtime of > your cluster. 3.0 will do this automatically . With 2.8, you have to dump > your collection, add a node and restore the collection. Please keep in mind > that the numOfShards could not be changed so that you have good value for > that from beginning. > > Also, these roadmap features are important to us, and I would like to know > if you have an estimate on when these features are expected to become > available? > > - Transaction isolation within a cluster > > Yes, it will come later this year. Hopefully in the first half of the year. > > - Automatic failover > > This will come with 3.0. ETA is May. > > - Master / master replication > > This will come with 3.0. ETA is May. > > - Rebalance > > This will come with 3.0. ETA is May. > > From the FAQ: > > Actually, ArangoDB doesn’t compete with massively distributed systems > like Cassandra with thousands of nodes and many terabytes of data. > > While we're not aiming at such a massively distributed system, we do need > a scalable db infrastructure. > Do you consider your clustering to be production ready? > > Short answer: yes > We have already happy customers who use an Arango Cluster in production. > As you see above, some features for the cluster are missing. 3.0 will bring > a lot of improvements and also the following releases. To give you a more > detailed answer it would be great to hear more about your use-case. Please > contact me at [email protected] <javascript:>. > > -- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
