Ok perfect thank you very much, this worked perfectly.
Once my agency is started the right way, everything works very well.
However, I now have a new problem related to failure modes: When i kill an
agent, wait, and start another agent to replace it, I get the following
error:
2017-01-16T17:45:31Z [1] INFO ArangoDB (version 3.1.8 [linux]) is ready for
business. Have fun!
2017-01-16T17:45:31Z [1] INFO {agency} Entering gossip phase ...
2017-01-16T17:45:31Z [1] INFO {agency} Adding
1d148ff1-e923-4f0e-9921-6818c2387822(tcp://arango-agent-2:5002) to agent
pool
2017-01-16T17:45:31Z [1] INFO {agency} Adding
72d76ea1-a67e-4cbe-add4-240bbba0ba93(tcp://arango-agent-3:5003) to agent
pool
2017-01-16T17:45:31Z [1] INFO {agency} Adding
c63e1c35-1349-480d-bb1f-7dfce40aa2af(tcp://arango-agent-1:5001) to agent
pool
2017-01-16T17:45:31Z [1] FATAL {agency} Too many peers in pool: 4>3
It looks like the agency does not detect that an agent was killed, so it
refuses the new agent. If anyone has an idea of what i Can do about that,
that would be helpful ! Thank you
Le mercredi 11 janvier 2017 09:37:26 UTC+1, Kaveh Vahedipour a écrit :
>
> Let me start off by saying that you cannot use zookeeper as an agency
> simply because of syntactic differences between zookeper and arangodb
> agency APIs.
>
> Now to your problem. I tried your startup and the only thing that is
> missing is "--agency.my-address" for every agency instance. As the log
> messages from agent 1 indicate, the connections are not attempted to
> "arango-agent-2:5002"
> and "arango-agent-3:5003" after handshake but to "localhost:5002" and
> "localhost:5003" respectively. So every agent should cary an additional
> parameter "--agency.my-address tcp://arango-agent-1:500<X>". Because of
> differences and ambiguities between frameworks, we had to introduce this
> additional command line argument.
>
> Your agency shouls starup just fine as follows:
>
> # 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 --agency.my-address
> tcp://arango-agent-1:5001
> # 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 --agency.my-address
> tcp://arango-agent-2:5002
> # 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.my-address
> tcp://arango-agent-3:5003 --agency.endpoint tcp://arango-agent-1:5001
> --agency.endpoint tcp://arango-agent-2:5002
>
>
>
--
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.
