Description
I'm using the latest ArangoDB of the respective release series:
- [ x ] 3.3 Milestone 2 Community Edition
Mode:
- [ x ] Cluster
There are 2 vms, each with 2 primary db servers and 2 coordinators. There are 5 agents, 3 on 1 vm, and 2 on the other
Storage-Engine:
- [ x ] mmfiles
On this operating system:
- [ x ] RedHat .rpm
The following problem occurs:
Using the same configuration that works for 3.2.2, after starting the agency, coordinators and db servers fail to completely startup. The processes run, but they never start listening on their ports. The last log from the db server is
2017-11-07T02:02:27Z [11599] INFO {cluster} Starting up with role PRIMARY
In the logs, you can see looping repeating requests from each of the db servers and coordinators that look like this:
2017-11-07T02:05:29Z [11386] INFO {requests} "http-request-end","0x7facfc6eba90","dbserver2:port","POST","HTTP/1.1",412,134,15,"/_api/agency/write",0.000139
2017-11-07T02:05:29Z [11386] INFO {requests} "http-request-end","0x7facfc6eba90","dbserver2:port","POST","HTTP/1.1",200,21,30,"/_api/agency/read",0.000062
2017-11-07T02:05:29Z [11386] INFO {requests} "http-request-end","0x7facfc6eba90","dbserver2:port","POST","HTTP/1.1",200,32,43,"/_api/agency/read",0.000050
2017-11-07T02:05:29Z [11280] INFO {requests} "http-request-end","0x7fed9c340a10","dbserver2:port","POST","HTTP/1.1",307,134,0,"/_api/agency/write",0.000121
Instead I would be expecting: them to startup