Simran

The primary index doesn't apply here. Traversals can utilize the edge index or vertex-centric indexes. The edge index was used for your query, and over 2.5M relations were processed. Depending...

The upcoming version 3.12.6 will include the fix.

@sajeevpr: is your data structure like this? ```json { "history": [ { "cc": "2016-11-15" }, { "cc": "2016-10-12" }, { "cc": "2016-11-22" } ] } ``` Note that comparing anything...

As a workaround for your current version, you can disable the `async-prefetch` optimizer rule, which should have the same effect as the upcoming bugfix. `curl -d '{ "query": "for i...

@Kafkalasch What version of ArangoDB do you use? Can you reproduce it with 3.11.0 or later?

FWIW, https://github.com/arangodb/arangodb/pull/17294 was supposed to fix this issue (3.11.0+) but there seems to be an additional issue with the cache invalidation and the RocksDB isolation. Related issue: #13943

`security_rules` is an array of objects, and there is at least one object where `access` is `"Allow"` and one where it is `"Deny"` in the document: ```js FOR v0 IN...

@matcho Just double-checking, you refer to the attribute `documentsSize` returned by `.figures()`, right? Do you have `--server.statistics` enabled? It would be worth a try what happens if you turn them...

Can you also check `engine-rocksdb/journals/archive`? The number of files in that folder is expected to remain more or less constant. If it's ever-growing then RocksDB might fail to delete old...

Thanks for confirming that the journal files aren't responsible for this. As long as the number of archived journals goes down again, it should be fine. But that means that...