ArangoDB: Errors in a cluster environment
See original GitHub issuejava.util.concurrent.CompletionException: com.arangodb.ArangoDBException: Response: 500, Error: 1521 - AQL: collection not known to traversal: 'operation'. please add 'WITH operation' as the first line in your AQL (while executing)
from the ArangoDB docs
From ArangoDB 3.1 onwards WITH is required for traversals in a clustered environment in order to avoid deadlocks.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Cluster | Troubleshooting | Manual | ArangoDB Documentation
Cluster front end is unresponsive. Check if the Coordinator(s) in question are started up. · Cluster front end announces errors on any number...
Read more >Error codes and meanings | Appendix | Manual - ArangoDB
General errors; HTTP error status codes; HTTP processing errors ... ArangoDB cluster errors; ArangoDB query errors; AQL user function errors ...
Read more >ArangoDB v3.8 Known Issues
If you are running a cluster and use a custom shard key on a collection (default is _key ) and you provide a...
Read more >Troubleshooting ArangoDB Server
Check the server log file: If the server has written a log file you should check it because it might contain relevant error...
Read more >Known Issues in ArangoDB 3.6
Description: The immediate recreation of ArangoSearch Analyzers in cluster deployments (deleting and shortly after creating one with the same name but different ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Seems like we have to find an alternative to AQL UDFs - https://github.com/arangodb/arangodb/issues/11271
@lokm01 could you please try the above PR? DB re-creation is required.