ArangoDB

• Fix SEARCH-465: Truncate on ArangoSearch index could release a WAL if commit passed.
• Updated ArangoDB Starter to 0.16.0.
• Avoid recursive lock during agency startup.
• Fixed issue with lock starvation when an AQL insert operation with multiple static documents was executed as part of a streaming transaction.
• Added startup option `--database.max-databases` to limit the maximum number of databases that can exist in parallel on a deployment. This option can be used to limit resources used by database objects. If the option is used and there already exist as many databases as configured by this option, any attempt to create an additional database will fail with error 32 (`ERROR_RESOURCE_LIMIT`). Additional databases can then only be created if other databases are dropped first. The default value for this option is unlimited, so technically an arbitrary amount of databases can be created (although effectively the number of databases is limited by memory and processing resources).
• FE-304, FE-305: use navigator.onLine for checking internet connection, correct path for running/slow queries.
• Enforce that server always returns an empty body if the return code is 204.
• Arangodump retries dump requests in more cases: read, write and connection errors.
• Whenever there is a query request timeout in AQL (e.g., a server died) which causes the query to fail, the DBServers will now all directly kill their potentially ongoing parts of the query and not wait for garbage collection.
• Use libunwind in jemalloc profiling to make it available with libmusl and static binaries.
• BTS-1331: Reduced the amount of required network calls when using traversals combined with FILTER and/or PRUNE statements in a GeneralGraph in ombination with a clustered environment.
• Added transparent LZ4 compression for values in the in-memory edge cache if their size exceeds a configurable threshold. This is configurable as an opt-in functionality.

Full changelog available here.