Hi, please note that there have been numerous bugfixes in 3.1.10 and that you should upgrade your installation.
Cheers, Willi On Monday, February 6, 2017 at 4:26:18 PM UTC+1, [email protected] wrote: > > Hi, > > the documentation was wrong. We forgot it to recheck these parts when we > did the 3.1 release. > > The missing piece in this setup is the missing --agency.my-address for the > agents (which is present in the local setup example but not in the > distributed). > > Without it the agents broadcast that they are reachable via localhost:* > which is of course wrong. > > This should work: > > arangod --server.endpoint tcp://0.0.0.0:5001 --agency.my-address tcp:// > 10.0.1.52 > <http://www.google.com/url?q=http%3A%2F%2F10.0.1.52&sa=D&sntz=1&usg=AFQjCNG4wayOUcRqtLBlSShTLHNdzTKexg>:5001 > --server.authentication > false --agency.activate true --agency.size 3 --agency.supervision true > --database.directory agency1 > arangod --server.endpoint tcp://0.0.0.0:5002 --agency.my-address tcp:// > 10.0.1.137:5002 --server.authentication false --agency.activate true > --agency.size 3 --agency.supervision true --database.directory agency2 > arangod --server.endpoint tcp://0.0.0.0:5003 --agency.my-address tcp:// > 10.0.1.228:5003 --server.authentication false --agency.activate true > --agency.size 3 --agency.endpoint tcp://10.0.1.52:5001 --agency.endpoint > tcp://10.0.1.137:5002 --agency.endpoint tcp://10.0.1.228:5003 > --agency.supervision > true --database.directory agency3 > > Am Samstag, 4. Februar 2017 05:15:21 UTC+1 schrieb [email protected]: >> >> Team, >> >> i am testing arangodb clustering with 3 machines of setup and i am >> following arangodb documentation as per link ( >> https://docs.arangodb.com/3.1/Manual/Deployment/Distributed.html). >> >> Below are steps/commands that i have tried on each machine one by one but >> its not resolving agency/cluster across machines. >> >> >> 10.0.1.52 >> <http://www.google.com/url?q=http%3A%2F%2F10.0.1.52&sa=D&sntz=1&usg=AFQjCNG4wayOUcRqtLBlSShTLHNdzTKexg> >> : >> arangod --server.endpoint tcp://0.0.0.0:5001 --server.authentication >> false --agency.activate true --agency.size 3 --agency.supervision true >> --database.directory agency1 & >> >> 10.0.1.137: >> arangod --server.endpoint tcp://0.0.0.0:5002 --server.authentication >> false --agency.activate true --agency.size 3 --agency.supervision true >> --database.directory agency2 & >> >> 10.0.1.228: >> arangod --server.endpoint tcp://0.0.0.0:5003 --server.authentication >> false --agency.activate true --agency.size 3 --agency.endpoint tcp:// >> 10.0.1.52:5001 --agency.endpoint tcp://10.0.1.137:5002 --agency.endpoint >> tcp://10.0.1.228:5003 --agency.supervision true --database.directory >> agency3 & >> >> >> 10.0.1.52: >> arangod --server.authentication=false --server.endpoint tcp:// >> 0.0.0.0:8529 --cluster.my-address tcp://10.0.1.52:8529 >> --cluster.my-local-info db1 --cluster.my-role PRIMARY >> --cluster.agency-endpoint tcp://10.0.1.52:5001 --cluster.agency-endpoint >> tcp://10.0.1.137:5002 --cluster.agency-endpoint tcp://10.0.1.228:5003 >> --database.directory primary1 & >> >> 10.0.1.137: >> arangod --server.authentication=false --server.endpoint tcp:// >> 0.0.0.0:8530 --cluster.my-address tcp:///10.0.1.137:8530 >> --cluster.my-local-info db2 --cluster.my-role PRIMARY >> --cluster.agency-endpoint tcp://10.0.1.52:5001 --cluster.agency-endpoint >> tcp://10.0.1.137:5002 --cluster.agency-endpoint tcp://10.0.1.228:5003 >> --database.directory primary2 & >> >> 10.0.1.228: >> arangod --server.authentication=false --server.endpoint tcp:// >> 0.0.0.0:8531 --cluster.my-address tcp://10.0.1.228:8531 >> --cluster.my-local-info coord1 --cluster.my-role COORDINATOR >> --cluster.agency-endpoint tcp://10.0.1.52:5001 --cluster.agency-endpoint >> tcp://10.0.1.137:5002 --cluster.agency-endpoint tcp://10.0.1.228:5003 >> --database.directory coordinator & >> >> >> >> i am getting below error every time on all machine: >> >> 2017-02-04T02:47:12Z [29952] INFO {agency} >> f5c1433a-cec2-4089-829e-1c42fef92942: following in term 58 >> 2017-02-04T02:47:13Z [29952] INFO {agency} >> f5c1433a-cec2-4089-829e-1c42fef92942: candidating in term 58 >> 2017-02-04T02:47:13Z [29952] INFO {cluster} cannot create connection to >> server '' at endpoint 'tcp://localhost:5002' >> 2017-02-04T02:47:13Z [29952] INFO {cluster} cannot create connection to >> server '' at endpoint 'tcp://localhost:5001' >> 2017-02-04T02:47:13Z [29952] INFO {agency} >> f5c1433a-cec2-4089-829e-1c42fef92942: following in term 59 >> 2017-02-04T02:47:15Z [29952] INFO {agency} >> f5c1433a-cec2-4089-829e-1c42fef92942: candidating in term 59 >> 2017-02-04T03:28:47Z [17164] ERROR {cluster} cannot create connection to >> server '' at endpoint 'tcp://localhost:5003' >> 2017-02-04T03:28:47Z [17164] ERROR {cluster} cannot create connection to >> server '' at endpoint 'tcp://localhost:5001' >> 2017-02-04T03:28:51Z [17164] ERROR {cluster} cannot create connection to >> server '' at endpoint 'tcp://localhost:5003' >> >> >> *Can anybody help out ...?* >> >> >> -- 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.
