Jan

Quick update: problem did not occur for me yet. Now trying some more variations to see if the problem is tied to a very specific condition.

Tried with v3.7.9 and more than 200 concurrent runs of creating and dropping random indexes on 2 different collections, and after each run checking the consistency across all indexes. This...

Ok, thanks, if you could provide me the exact index information (i.e. type, attribute names, uniqueness, sparseness, ideally some example attribute data) for at least one of the affected indexes...

@AntoineAA : no update here. I tried reproducing the issue locally for a few days, but without any luck. What I can say for sure is that we did not...

Thanks for reporting this issue. Currently the optimizer will pick indexes based on how many attributes of the `FILTER` / `SORT` conditions are covered by an index, how selective an...

Hi @979357361 , have you tried stripping the `librocksdb.a` library after it was built? Here are results from a local build of mine (x86_64, `make static_lib`), using latest RocksDB: ```...

@979357361 : I can't say much about building the shared library, because I never tried to do so myself. Regarding stripping: if you link the RocksDB library to your executable,...

Side note: I tried the change to check if it would fix https://github.com/facebook/rocksdb/issues/9762 as well, but it doesn't.

@DenisBytes : thank you for reporting this issue. We have reproduced it and are currently looking into it.

Fixed via https://github.com/arangodb/arangodb/pull/21145 / https://github.com/arangodb/arangodb/pull/21147 The fix will be included as part of 3.12.1.