On further checking, we found these errors on the primary log file:

2017-01-02T11:34:59Z [32130] ERROR {heartbeat} Current/Version in agency is 
not an integer.
2017-01-02T11:34:59Z [32130] ERROR {heartbeat} Plan Version is not a 
number! "(non-representable type none)"

On Tuesday, January 3, 2017 at 11:30:09 AM UTC+5:30, 
[email protected] wrote:
>
> We currently setup ArangoDB 3.0.12 in the Centos machines, but the cluster 
> seems to go down within a days time and
> we are not able to recover it. The cluster was setup based on these 
> instructions : 
> https://docs.arangodb.com/3.0/Manual/Deployment/Distributed.html 
>
> This has happened even when no data is loaded into the machines.
>
> This is the message we received on the ArangoDB agency log file :
>
> [32108] WARNING maximal body size is 1073741824, request body size is 
> 1260911905
>
>
> Thanks,
> Praveen.
>

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