We are currently testing ArangoDB3.0.6 for a POC. We are using 3 AWS 
m3.large machines. We set up a cluster of 1 coordinator and 2 DB servers.

Following are the commands used to bring up the cluster.

Starting Server Agency :

*DB server - 1:*

sudo arangod --server.endpoint tcp://0.0.0.0:5001 --server.authentication 
false --agency.id 0 --agency.size 3 --agency.supervision true agency1 &

*DB server - 2 :*

sudo arangod --server.endpoint tcp://0.0.0.0:5002 --server.authentication 
false --agency.id 1 --agency.size 3 --agency.supervision true agency2 &

*Co-ordinator :*

sudo arangod --server.endpoint tcp://0.0.0.0:5003 --server.authentication 
false --agency.id 2 --agency.size 3 --agency.endpoint tcp://:5001 
--agency.endpoint tcp://:5002 --agency.endpoint tcp://:5003 --agency.notify 
true --agency.supervision true agency3 &


Then we started the arangodb service by following commands:

*DB server1 :*

sudo arangod --server.authentication=false --server.endpoint 
tcp://0.0.0.0:8529 --cluster.my-address tcp://:8529 --cluster.my-local-info 
db1 --cluster.my-role PRIMARY --cluster.agency-endpoint tcp://:5001 
--cluster.agency-endpoint tcp://:5002 --cluster.agency-endpoint tcp://:5003 
primary1 &

*DB Server2 :*

sudo arangod --server.authentication=false --server.endpoint 
tcp://0.0.0.0:8530 --cluster.my-address tcp://:8530 --cluster.my-local-info 
db2 --cluster.my-role PRIMARY --cluster.agency-endpoint tcp://:5001 
--cluster.agency-endpoint tcp://:5002 --cluster.agency-endpoint tcp://:5003 
primary2 &

*Co-ordinator :*

sudo arangod --server.authentication=false --server.endpoint 
tcp://0.0.0.0:8531 --cluster.my-address tcp://:8531 --cluster.my-local-info 
coord1 --cluster.my-role COORDINATOR --cluster.agency-endpoint tcp://:5001 
--cluster.agency-endpoint tcp://:5002 --cluster.agency-endpoint tcp://:5003 
coordinator &

Using the WebUI we are able to create the collections and graphs. We 
uploaded around 100Million nodes and created edges. When we tried to 
truncate the edges we see the server going down. Not able to access the 
data after that. When we tried restarting the server by following the above 
mentioned steps we got the following info in logs: From DB server2: INFO 
cannot create connection to server '' at endpoint 'tcp://:5003' INFO cannot 
create connection to server '' at endpoint 'tcp://:5001'

We dont want to lose the data in the database. So we would like to know 
about the following things. 

a) How to bring the coordinator and the DB servers back ? 

b) Previously we used to delete agency and coordinator folder from 
Co-ordinator and agency and primary* folder from DBservers to bring back 
the server and create the database again. Is there a way we can restore the 
database again ?


Thanks 

-- 
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.

Reply via email to