CODEWITHSUNDEEP
arangodb
ile
ile

Reputation: 1805

How do I start ArangoDB cluster in active failover mode?

I try to follow this, but I can't seem to make it work: https://docs.arangodb.com/3.11/deploy/deployment/active-failover/manual-start/

ArangoDB version 3.3.7.

I try to start 3 nodes (3 agents). I believe officially I can start only 2 dbservers, but I heard 3 dbservers should also work.

Upvotes: 1

Views: 631

Answers (2)

Kaveh Vahedipour
Kaveh Vahedipour

Reputation: 3477

Please use the ArangoDB starter to start an ActiveFailover deployment here https://docs.arangodb.com/3.11/deploy/deployment/active-failover/using-the-arangodb-starter/

Or the cluster, where you may employ arbitrary numbers of db servers and coordinators here: https://docs.arangodb.com/3.11/deploy/deployment/cluster/

Upvotes: 0

ile
ile

Reputation: 1805

Ok, it wasn't easy, but here are the commands. Note that you probably don't want to expose the database to the world without authentication (and maybe traffic encryption).

Server 1 (172.31.54.123):

arangod --server.endpoint tcp://172.31.54.123:8531 --server.storage-engine rocksdb --database.directory /data/agent --uid arangodb --gid arangodb --server.jwt-secret verysecret --log.file /data/agent.log --log.force-direct false --foxx.queues false --server.statistics false --agency.activate true --agency.size 3 --agency.supervision true --agency.my-address tcp://172.31.54.123:8531 --agency.endpoint tcp://172.31.63.137:8531 --agency.endpoint tcp://172.31.48.49:8531

arangod --server.endpoint tcp://172.31.54.123:8529 --server.storage-engine rocksdb --database.directory /data/arangodb --uid arangodb --gid arangodb --server.jwt-secret verysecret --log.file /data/arangod.log --log.force-direct false --foxx.queues false --server.statistics true --replication.automatic-failover true --cluster.my-address tcp://172.31.54.123:8529 --cluster.my-role SINGLE --cluster.agency-endpoint tcp://172.31.54.123:8531 --cluster.agency-endpoint tcp://172.31.63.137:8531 --cluster.agency-endpoint tcp://172.31.48.49:8531

Server 2 (172.31.63.137):

arangod --server.endpoint tcp://172.31.63.137:8531 --server.storage-engine rocksdb --database.directory /data/agent --uid arangodb --gid arangodb --server.jwt-secret verysecret --log.file /data/agent.log --log.force-direct false --foxx.queues false --server.statistics false --agency.activate true --agency.size 3 --agency.supervision true --agency.my-address tcp://172.31.63.137:8531 --agency.endpoint tcp://172.31.63.137:8531 --agency.endpoint tcp://172.31.48.49:8531

arangod --server.endpoint tcp://172.31.63.137:8529 --server.storage-engine rocksdb --database.directory /data/arangodb --uid arangodb --gid arangodb --server.jwt-secret verysecret --log.file /data/arangod.log --log.force-direct false --foxx.queues false --server.statistics true --replication.automatic-failover true --cluster.my-address tcp://172.31.63.137:8529 --cluster.my-role SINGLE --cluster.agency-endpoint tcp://172.31.54.123:8531 --cluster.agency-endpoint tcp://172.31.63.137:8531 --cluster.agency-endpoint tcp://172.31.48.49:8531

Server 3 (172.31.48.49):

arangod --server.endpoint tcp://172.31.48.49:8531 --server.storage-engine rocksdb --database.directory /data/agent --uid arangodb --gid arangodb --server.jwt-secret verysecret --log.file /data/agent.log --log.force-direct false --foxx.queues false --server.statistics false --agency.activate true --agency.size 3 --agency.supervision true --agency.my-address tcp://172.31.48.49:8531 --agency.endpoint tcp://172.31.63.137:8531 --agency.endpoint tcp://172.31.48.49:8531

arangod --server.endpoint tcp://172.31.48.49:8529 --server.storage-engine rocksdb --database.directory /data/arangodb --uid arangodb --gid arangodb --server.jwt-secret verysecret --log.file /data/arangod.log --log.force-direct false --foxx.queues false --server.statistics true --replication.automatic-failover true --cluster.my-address tcp://172.31.48.49:8529 --cluster.my-role SINGLE --cluster.agency-endpoint tcp://172.31.54.123:8531 --cluster.agency-endpoint tcp://172.31.63.137:8531 --cluster.agency-endpoint tcp://172.31.48.49:8531

IP addresses will of course be different, but overall this should work.

Upvotes: 1

Related Questions