ArangoDB3 - Three Node Cluster without DCOS

367 views
Skip to first unread message

Nick Pavlica

unread,
Jul 12, 2016, 6:24:54 PM7/12/16
to ArangoDB
All,
  I would like to configure a three node cluster without DCOS.  The current docs, only mention the command line switches(https://docs.arangodb.com/3.0/Manual/Administration/Configuration/Cluster.html), and when I when I look at the arangod.conf file, I don't see any cluster configuration options for the cluster end points.  Can  you provide an example arangodb.conf file with an example 3 node cluster configuration?  This would be a nice addition to the docs and possibly a blog post.

Thanks!
--Nick

Wilfried Gösgens

unread,
Jul 13, 2016, 4:33:12 AM7/13/16
to ArangoDB
Hi Nick,
in general all arangodb commandline options map into the configuration file.

so running
  arangodb --help-all
and browsing through the list...
...
Section 'cluster' (Configure the cluster)
  --cluster.agency-endpoint <string...>                 agency endpoint to connect to (default: )
  --cluster.agency-prefix <string>                      agency prefix (default: "")
...

would translate to

[cluster]
agency-endpoint = tcp://192.168.1.1:4001
agency-prefix = mycluster

Hope this helps

Cheers,
Willi

Nick Pavlica

unread,
Jul 13, 2016, 3:10:40 PM7/13/16
to ArangoDB
Hi Willi,
  I'm having some issues getting the server to start once I change the arangod.conf to reflect the cluster settings:


[cluster]
data-path = /var/lib/arangodb3/cluster
log-path = /var/log/arangodb3/cluster
arangod-path = @SBINDIR@/arangod@PROGRAM_SUFFIX@
dbserver-config = @SYSCONFDIR@/arangod.conf
coordinator-config = @SYSCONFDIR@/arangod.conf
agency-prefix = agency1 
agency-id = 0
agency-size = 3
agency-notify true
server-authentication = false
server-endpoint = tcp://192.168.185.37:5001
agency-endpoint = tcp://192.168.185.37:5001
agency-endpoint = tcp://192.168.162.221:5001
agency-endpoint = tcp://192.168.205.156:5001

I'm not sure where to go next with the configuration.  Any guidance would be appreciated.

-- Nick

Wilfried Gösgens

unread,
Jul 14, 2016, 6:10:10 AM7/14/16
to ArangoDB
Hi Nick,
the @@ strings are replaced during the build process by cmake.
You have to provide the actual directories there to make it work - i.e. @SYSCONFDIR@ -> /etc/arangodb3/

Cheers,
Willi

Nick Pavlica

unread,
Jul 14, 2016, 1:29:05 PM7/14/16
to ArangoDB
All,
   I've updated the arangod.conf file to reflect default Ubuntu install locations replacing the @SYSCONFDIR@.  However, the server still fails to restart with this configuration.  I believe that I have all the necessary agency configuration done according to these docs  (https://docs.arangodb.com/3.0/Manual/Deployment/Local.html) and this thread.  I'm sure it's something simple, be we are missing something here..?

.....
[cluster]
data-path = /var/lib/arangodb3/cluster
log-path = /var/log/arangodb3/cluster
#arangod-path = @SBINDIR@/arangod@PROGRAM_SUFFIX@
arangod-path = /usr/sbin/arangod
#dbserver-config = @SYSCONFDIR@/arangod.conf
dbserver-config = /etc/arangodb3/arangod.conf
#coordinator-config = @SYSCONFDIR@/arangod.conf
coordinator-config = /etc/arangodb3/arangod.conf
########  Attempt to configure a cluster ######
agency-prefix = agency1
agency-id = 0
agency-size = 3
agency-notify true
server-authentication = false
server-endpoint = tcp://192.168.185.37:5001
agency-endpoint = tcp://192.168.185.37:5001
agency-endpoint = tcp://192.168.162.221:5001
agency-endpoint = tcp://192.168.205.156:5001


-- Nick

kishor...@games24x7.com

unread,
Aug 30, 2017, 7:34:03 AM8/30/17
to ArangoDB
Hi Nick,

Have u got this worked?

Even i'm trying to setup a cluster with three nodes having all the three (agency,db,coordinator) on all.

Process running,but i dont think cluster is up and running.

Got below INFO,

INFO {agencycomm} Flaky agency communication to http+tcp://IP1:5001. Unsuccessful consecutive tries: 50 (97.28s). Network checks advised
INFO {agencycomm} Flaky agency communication to http+tcp://IP2:5001. Unsuccessful consecutive tries: 50 (97.28s). Network checks advised
INFO {agencycomm} Flaky agency communication to http+tcp://IP3:5001. Unsuccessful consecutive tries: 50 (97.28s). Network checks advised

any help would be appreciated.

Thanks,
Kishore 
Reply all
Reply to author
Forward
0 new messages