Hi Max, That's great! Please let me know when you have more information regarding arangojs.
I have one last question for now: Will it be possible to mix different versions of ArangoDB in the same cluster? This would make it a lot easier to upgrade to a newer version of ArangoDB. Bart On Thursday, May 26, 2016 at 1:10:31 AM UTC+2, Max Neunhoeffer wrote: > > Hi Bart, > We definitely plan to push out 3.0 early in June. > Your question about arangojs is a good one. I would guess that the answer > is "no" at this stage. However, I will contact the author Alan and ask him. > This should definitely be added and should not be much trouble. The client > code would have to specify two or more endpoints of coordinators when the > connection is made initially and from then on the failover can be > transparent to the client. > > Cheers, > Max > > Am 25. Mai 2016 23:50:12 MESZ, schrieb Bart DS <[email protected] > <javascript:>>: > >Hi Max, > > > >This sounds very promising! > >What's the estimated timeframe for the 3.0 release? > > > >Regarding client connections, is the official arangojs client cluster > >aware? > >In other words, is it able to survive server / coordinator / host > >failures > >in the cluster by connecting to a different host / coordinator in such > >situations? > > > >Thanks, > > > >Bart > > > > > >On Wednesday, May 25, 2016 at 11:11:37 PM UTC+2, [email protected] > >wrote: > >> > >> Hi Bart, > >> > >> Max from ArangoDB here. We are putting the finishing touches on the > >3.0 > >> release basically as we speak. Good cluster setup documentation is > >> unfortunately one of the things we are still missing, but we will > >> definitely have this in place for the release. > >> > >> Am Mittwoch, 25. Mai 2016 22:49:17 UTC+2 schrieb Bart DS: > >>> > >>> Hi Willi, > >>> > >>> Thanks for this very detailed explanation. > >>> If I understand correctly, I can set up an ArangoDB 3.0 cluster > >without > >>> any orchestration framework (such as Mesos) ? > >>> > >> Yes, the startup process has been simplified a lot for 3.0. You > >basically > >> have to fire up a bunch of Docker containers (all with the same > >image) with > >> certain command line options. Everything else organises itself within > >the > >> ArangoDB cluster. We will publish a blog post shortly after the > >release to > >> explain how this is done. > >> > >>> When using asynchronous replication there will be no automatic > >failover > >>> or rebalancing (yet), but when using synchronous replication I will > >have > >>> automatic failover and rebalancing out of the box? > >>> > >> Yes, all of this is done within the ArangoDB cluster thanks to our > >own > >> implementation of the Raft consensus protocol. The only thing it > >cannot do > >> on its own is restart containers or launch new ones. And automatic > >failover > >> for the asynchronous replication within the ArangoDB cluster will > >only land > >> with 3.1. > >> > >>> > >>> So if I have e.g. 5 servers in the cluster and one server goes down, > >one > >>> (or more?) of the other 4 servers will take over the tasks of the > >failing > >>> server and all reads/writes will still succeed? > >>> Is that correct? > >>> > >> Exactly so. And due to synchronous replication you will not lose > >committed > >> and confirmed data. > >> > >>> > >>> Also, If I run 3.0 on another orchestration framework, will I be > >able to > >>> dynamically add/remove servers to/from the cluster already? Or isn't > >that > >>> possible yet?out > >>> > >> You can simply start new Docker containers to add more coordinators > >or > >> DBServers. You can simply kill coordinators without losing anything. > >> You can ask the ArangoDB cluster to clean out a DBserver in a > >controlled > >> fashion such that its data is relocated to other servers > >automatically. > >> Once this has completed, you can simply kill the DBServer by stopping > >its > >> Docker container. > >> > >>> > >>> Can you point me to any documentation on how to set up such a > >cluster > >>> with ArangoDB 3.0? > >>> > >> Unfortunately, this is not yet written. I do have a bash script which > > > >> launches a cluster locally just using docker containers. I attach the > > > >> script such that you can see how things will work. This uses the > >3.0.0b3 > >> which we are about to publish. Note that in this not all of the above > > > >> mentioned features work yet. > >> > >> Cheers, > >> Max. > >> > >>> > >>> Bart > >>> > >> > > > >-- > >You received this message because you are subscribed to a topic in the > >Google Groups "ArangoDB" group. > >To unsubscribe from this topic, visit > >https://groups.google.com/d/topic/arangodb/WHedmT2mkoE/unsubscribe. > >To unsubscribe from this group and all its topics, send an email to > >[email protected] <javascript:>. > >For more options, visit https://groups.google.com/d/optout. > > -- 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.
