Dear OrientDB team and community,
I would like to implement an architecture with one Master on Physical
Machine and many replica on containers in order to scale on traffic peaks
(Orientdb version is 2.2.31).
So we have one file *default-distributed-db-config.json* for the master
{
"autoDeploy": true,
"executionMode": "undefined",
"readQuorum": 1,
"writeQuorum": "1",
"readYourWrites": true,
"newNodeStrategy": "static",
"servers": {
"orient_master": "master",
"orient_replica_container_1": "replica",
...
"orient_replica_container_N": "replica"
},
"clusters": {
"*": { "servers" : [ "<NEW_NODE>" ] }
}
}
and one for each of the replicas
{
"autoDeploy": true,
"executionMode": "undefined",
"readQuorum": 1,
"writeQuorum": "1",
"readYourWrites": true,
"newNodeStrategy": "static",
"servers": {
"orient_master": "master",
"orient_replica_container_1": "replica",
...
"orient_replica_container_N": "replica"
},
"clusters": {
"*": { "servers" : [ "<NEW_NODE>" ] }
}
}
The node *"orient_master": "master" *is common and predefined*.*
*If we don't put in each default-distributed-db-config.json file all the
info about the replicas they join the cluster as master.*
Is there any way, with this configuration, to let replicas auto-discover
master and master how to discover replicas?
Thanks in advance.
Roberto
--
---
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.
