New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
arangodb stopped responding (Arangodb 2.7.0 on OS X) #1571
Comments
If I see that correctly, you're running 4 queries, at least one of them is a join. Another possible pittfall is that you're doing a join with non existing attributes - which then in term will all become true, so you'll get the square of the two collections, which takes a lot of computing time and memory. |
Thanks for the prompt reply. As I was running ad-hoc queries, I'm sure you're right that I got it executing four 'pathological' queries simultaneously which meant any further queries would be queued behind them until they timed out. I do want to be able to run ad-hoc queries on a slave instance and it's always possible I'll send some bad ones. One way I should be able to mitigate this is by making the timeout more aggressive - I see there is a config setting for arangosh, but is it possible to set the request timeout when making HTTP AQL calls via the Cursor API either on a per-request or at a global server level? I can't find a setting in the documentation. Also it looks like the 'Cancel' button when running a query in the aadvark web UI doesn't stop the execution - I suggest that would be a good idea. |
Will be part of 2.8 - Thanks for reporting. |
We're looking at using arangodb for our application, and have created a proof-of-concept. While testing some large AQL queries from the web interface, arandod pegged up to full CPU and is no longer responsive - http://localhost:8529 doesn't respond and if I connect by commandline it gets as far as: "Connected to ArangoDB 'tcp://127.0.0.1:8529' version: 2.7.0 [standalone], database: '_system', username: 'root'" and doesn't display anything further.
I wasn't running any change to the database or collection structure at the same time. This is obviously a bit worrying were the same thing to happen in production!
Here is a list of threads running at the time:
The text was updated successfully, but these errors were encountered: