Description
Hello there,
We're running 2.7.3 and 2.6.12 on CentOS6 in four seperate production environments respectively, and we are able to consistently make ArangoDB stop responding with a pretty generic workload we put on it on every single one of them.
(Linux tat1234 2.6.32-573.el6.x86_64 #1 SMP Thu Jul 23 15:44:03 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux)
Attempting to 'arangosh' into the instance, does not return a prompt back nor does the dashboard on port 8529 respond.
I did an strace -p -f on the arangod process and I'm not sure what I'm actually looking at, but it doesn't seem TOO out of the ordinary compared to a responding instance:
http://hastebin.com/raw/erujuhewec
I was thinking it could be a behaviour of garbage collection, but it doesn't respond even after leaving it for hours. The only thing that fixes it would be to restart the daemon.
I'm clueless as to what steps are to be taken next. Help is much appreciated :)
Thanks in advance,
Otto