While the docs refer to a 4 node cluster in the section titled Limitations
running distributed
<https://orientdb.com/docs/last/Limits.html#limitations-running-distributed> I
suspect that it would be advisable to run a three node cluster so that a
majority can be reached when attempting to resolve inconsistencies.
I'd be greatly appreciative if a Orient guru could speak to whether or not
my assumption is correct.
Adam
On Thursday, August 13, 2015 at 7:19:51 AM UTC-7, Ran Mizrachi wrote:
>
> Hi,
>
> I'm running 2 VMs in Windows Azure cloud services.
> I would like to have 2 master nodes that will act as a hot backup of each
> other (because Windows Azure can take down machine at any time for updates
> purposes...)
> Therefore, i'm looking for configuration that will keep my nodes synced
> with all of my data all the time.
> I'm using v2.0.13.
>
> My current configuration is:
> {
> "autoDeploy": true,
> "hotAlignment": true,
> "executionMode": "asynchronous",
> "readQuorum": 1,
> "writeQuorum": 2,
> "failureAvailableNodesLessQuorum": false,
> "readYourWrites": true,
> "clusters": {
> "internal": {
> },
> "index": {
> },
> "*": {
> "servers" : [ "<NEW_NODE>" ]
> }
> }
> }
>
> During my tests I took 1 machine off, inserted some records and brought
> the node back online.
> I see that the nodes didn't sync. even though the hotAlignment is set to
> true - the new records was not copied to the other node.
>
> What am I missing?
>
> Thanks!
>
>
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" 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.
