|
From: Adam R. <ad...@ex...> - 2018-01-11 20:51:11
|
The replication in eXist as it is works using JMS and an appropriate Message Broker Service (typically Apache ActiveMQ) is used. If you want to do HA, you would need to add some mechanics: 1. A mechanism for discovering a dead-master 2. A mechanism for promoting a slave to a master (and likely reconfiguring some JMS stuff) 3. I could only see this working with READ access. If the writable master crashes, I have no idea how you would continue the writes on a slave-which-was-promoted-to-master with eXist. How to maintain database integrity? On 9 January 2018 at 13:44, Akram Ben Aissi <akr...@gm...> wrote: > Hi all, > > The eXist-db documentation states that eXists is for now single server, > and that it supports data replication in master-slave mode. > > > I want to build a Highly-Available cluster for eXist. Is there any > possibility to make the data replication use an elected master ? > The idea behind is to integrate it with zookeeper, unless someone did > already the job. > > Do you have any other feedback about eXist in HA architecture ? > > Akram > > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Exist-development mailing list > Exi...@li... > https://lists.sourceforge.net/lists/listinfo/exist-development > > -- Adam Retter eXist Core Developer { United Kingdom / United States } ad...@ex... |