Hi,
I have a script that deploys an arangodb cluster on a docker swarm. This
script used to work perfectly with arangodb 3.0.x. However it seems to fail
since 3.1, with the following error:
2017-01-10T16:51:26Z [1] INFO using endpoint 'http+tcp://0.0.0.0:5001' for
non-encrypted requests
2017-01-10T16:51:26Z [1] INFO ArangoDB (version 3.1.7 [linux]) is ready for
business. Have fun!
2017-01-10T16:51:27Z [1] INFO {agency} Entering gossip phase ...
2017-01-10T16:51:29Z [1] INFO {agency} Adding
0be3be42-10d6-4d88-a032-2c9f52c8e241(tcp://localhost:5003) to agent pool
2017-01-10T16:51:30Z [1] INFO {agency} Adding
2e90441b-8bc3-4df4-876c-2dececa0e052(tcp://localhost:5002) to agent pool
2017-01-10T16:51:31Z [1] ERROR {cluster} cannot create connection to server
'' at endpoint 'tcp://localhost:5003'
2017-01-10T16:51:31Z [1] ERROR {cluster} cannot create connection to server
'' at endpoint 'tcp://localhost:5002'
2017-01-10T16:51:35Z [1] ERROR {cluster} cannot create connection to server
'' at endpoint 'tcp://localhost:5003'
2017-01-10T16:51:35Z [1] ERROR {cluster} cannot create connection to server
'' at endpoint 'tcp://localhost:5002'
Here is the script that is broken since 3.1:
# Agent 1
docker service create --name arango-agent-1 --restart-max-attempts
${ARANGODB_RETRIES} --env ARANGO_ROOT_PASSWORD=${ARANGODB_PASSWORD}
--network arango-network --constraint 'node.hostname==node1.local.lan'
--replicas 1 arangodb:3.1.7 arangod --server.endpoint tcp://0.0.0.0:5001
--server.authentication ${ARANGODB_AUTH} --server.jwt-secret
${ARANGO_JWT_SECRET} --agency.size 3 --agency.supervision true
--agency.activate true
# Agent 2
docker service create --name arango-agent-2 --restart-max-attempts
${ARANGODB_RETRIES} --env ARANGO_ROOT_PASSWORD=${ARANGODB_PASSWORD}
--network arango-network --constraint 'node.hostname==node1.local.lan'
--replicas 1 arangodb:3.1.7 arangod --server.endpoint tcp://0.0.0.0:5002
--server.authentication ${ARANGODB_AUTH} --server.jwt-secret
${ARANGO_JWT_SECRET} --agency.size 3 --agency.supervision true
--agency.activate true
# Agent 3
docker service create --name arango-agent-3 --restart-max-attempts
${ARANGODB_RETRIES} --env ARANGO_ROOT_PASSWORD=${ARANGODB_PASSWORD}
--network arango-network --constraint 'node.hostname==node1.local.lan'
--replicas 1 arangodb:3.1.7 arangod --server.endpoint tcp://0.0.0.0:5003
--server.authentication ${ARANGODB_AUTH} --server.jwt-secret
${ARANGO_JWT_SECRET} --agency.size 3 --agency.supervision true
--agency.activate true --agency.endpoint tcp://arango-agent-1:5001
--agency.endpoint tcp://arango-agent-2:5002 --agency.endpoint
tcp://arango-agent-3:5003
Any idea on this ? I think it might be related to docker swarm network
layers, but It used to work on 3.0...
Also, is there a way to use zookeeper instead of a arangodb agency ? This
would be helpful since my zookeeper cluster works just fine already.
Thank you very much
--
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.
