ArangoDB v3.13 is under development and not released yet. This documentation is not final and potentially incomplete.

Known Issues in ArangoDB 3.12

Important issues affecting the 3.12.x versions of the ArangoDB suite of products

Note that this page does not list all open issues.

ArangoSearch

Issue
Date Added: 2018-12-19 Component: ArangoSearch Deployment Mode: Single-server Description: Value of `_id` attribute indexed by `arangosearch` View may become inconsistent after renaming a collection Affected Versions: 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x Fixed in Versions: - Reference: arangodb/backlog#514 (internal)
Date Added: 2018-12-03 Component: ArangoSearch Deployment Mode: Cluster Description: Score values evaluated by corresponding score functions (BM25/TFIDF) may differ in single-server and cluster with a collection having more than 1 shard Affected Versions: 3.4.x, 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x Fixed in Versions: - Reference: arangodb/backlog#508 (internal)
Date Added: 2018-12-03 Component: ArangoSearch Deployment Mode: All Description: Using a loop variable in expressions within a corresponding SEARCH condition is not supported Affected Versions: 3.4.x, 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x Fixed in Versions: - Reference: arangodb/backlog#318 (internal)
Date Added: 2019-06-25 Component: ArangoSearch Deployment Mode: All Description: The `primarySort` attribute in `arangosearch` View definitions cannot be set via the web interface. The option is immutable, but the web interface does not allow to set any View properties upfront (it creates a View with default parameters before the user has a chance to configure it). Affected Versions: 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x Fixed in Versions: - Reference: N/A
Date Added: 2020-03-19 Component: ArangoSearch Deployment Mode: All Description: Operators and functions in `SEARCH` clauses of AQL queries which compare values such as `>`, `>=`, `<`, `<=`, `IN_RANGE()` and `STARTS_WITH()` neither take the server language (`--default-language`) nor the Analyzer locale into account. The alphabetical order of characters as defined by a language is thus not honored and can lead to unexpected results in range queries. Affected Versions: 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x Fixed in Versions: - Reference: arangodb/backlog#679 (internal)

AQL

Issue

Issue
Date Added: 2018-09-05 Component: AQL Deployment Mode: Cluster Description: In a very uncommon edge case there is an issue with an optimization rule in the cluster. If you are running a cluster and use a custom shard key on a collection (default is `_key`) and you provide a wrong shard key in a modifying query (`UPDATE`, `REPLACE`, `DELETE`) and the wrong shard key is on a different shard than the correct one, a `DOCUMENT NOT FOUND` error is returned instead of a modification (example query: `UPDATE { _key: "123", shardKey: "wrongKey"} WITH { foo: "bar" } IN mycollection`). Note that the modification always happens if the rule is switched off, so the suggested workaround is to deactivate the optimizing rule `restrict-to-single-shard`. Affected Versions: 3.4.x, 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x Fixed in Versions: - Reference: arangodb/arangodb#6399

Date Added: 2018-09-05
Component: AQL
Deployment Mode: Cluster
Description: In a very uncommon edge case there is an issue with an optimization rule in the cluster. If you are running a cluster and use a custom shard key on a collection (default is _key) and you provide a wrong shard key in a modifying query (UPDATE, REPLACE, DELETE) and the wrong shard key is on a different shard than the correct one, a DOCUMENT NOT FOUND error is returned instead of a modification (example query: UPDATE { _key: "123", shardKey: "wrongKey"} WITH { foo: "bar" } IN mycollection). Note that the modification always happens if the rule is switched off, so the suggested workaround is to deactivate the optimizing rule restrict-to-single-shard.
Affected Versions: 3.4.x, 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x
Fixed in Versions: -
Reference: arangodb/arangodb#6399

Upgrading

Issue
Date Added: 2019-05-16 Component: arangod Deployment Mode: All Description: Bugfix release upgrades such as 3.4.4 to 3.4.5 may not create a backup of the database directory even if they should. Please create a copy manually before upgrading. Affected Versions: 3.4.x, 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x Fixed in Versions: - Reference: arangodb/planning#3745 (internal)
Date Added: 2023-06-06 Component: arangod Deployment Mode: Cluster Description: During a cluster upgrade while the supervision is deactivated (maintenance mode), upgraded DB-Server nodes are incorrectly reported to still have the old server version. The versions are visible in the Agency as well as in the Nodes section of the web interface. Affected Versions: 3.9.x, 3.10.x, 3.11.x, 3.12.x Fixed in Versions: - Reference: BTS-1409 (internal)

Issue

Date Added: 2019-05-16
Component: arangod
Deployment Mode: All
Description: Bugfix release upgrades such as 3.4.4 to 3.4.5 may not create a backup of the database directory even if they should. Please create a copy manually before upgrading.
Affected Versions: 3.4.x, 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x
Fixed in Versions: -
Reference: arangodb/planning#3745 (internal)

Date Added: 2023-06-06
Component: arangod
Deployment Mode: Cluster
Description: During a cluster upgrade while the supervision is deactivated (maintenance mode), upgraded DB-Server nodes are incorrectly reported to still have the old server version. The versions are visible in the Agency as well as in the Nodes section of the web interface.
Affected Versions: 3.9.x, 3.10.x, 3.11.x, 3.12.x
Fixed in Versions: -
Reference: BTS-1409 (internal)

Hot Backup

Issue
Date Added: 2019-10-09 Component: arangobackup Deployment Mode: All Description: The startup option `--operation` works as positional argument only, e.g. `arangobackup list`. The alternative syntax `arangobackup --operation list` is not accepted. Affected Versions: 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x Fixed in Versions: - Reference: N/A

Other

Issue
Date Added: 2019-04-03 Component: arangod Deployment Mode: Cluster Description: Updating the properties of a collection in the cluster may return before the properties are updated consistently on all shards. This is especially visible when setting a schema for a collection with multiple shards, and then instantly starting to store non-conforming documents into the collection. These may be accepted until the properties change has been fully propagated to all shards. Affected Versions: 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x Fixed in Versions: - Reference: N/A
Date Added: 2021-04-07 Component: arangod Deployment Mode: All Description: The Batch API (HTTP endpoint `/_api/batch`) cannot be used in combination with Stream transactions to submit batched requests, because the required header `x-arango-trx-id` is not forwarded. It only processes `Content-Type` and `Content-Id`. Affected Versions: 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x Fixed in Versions: - Reference: arangodb/arangodb#13552
Date Added: 2022-09-29 Component: ArangoDB Starter Deployment Mode: All Description: The ArangoDB Starter may fail to pick a Docker container name from cgroups. Affected Versions: 3.8.x, 3.9.x, 3.10.x, 3.11.x, 3.12.x Fixed in Versions: - Reference: GT-207 (internal)
Date Added: 2024-03-21 Component: arangod Deployment Mode: All Description: When creating an `inverted` index with the `inBackground` option enabled, HTTP API calls like `http://localhost:8529/_api/index?collection=<coll>&withHidden=true` don’t return the `isBuilding` and `progress` attributes and the progress of the index building can thus not be observed. Affected Versions: 3.10.13, 3.11.7, 3.12.x Fixed in Versions: - Reference: BTS-1788 (internal)
Date Added: 2024-03-28 Component: arangod Deployment Mode: Cluster Description: During startup or upgrade from a previous minor version, Agent nodes crash if the `--cluster.force-one-shard` option is enabled. Workaround: Don’t use the `--cluster.force-one-shard` option (or set it to `false`) for Agents. Affected Versions: 3.12.0 Fixed in Versions: 3.12.1 Reference: BTS-1839 (internal)
Date Added: 2024-03-28 Component: arangod Deployment Mode: Cluster Description: In a cluster, creating an EnterpriseGraph fails in OneShard databases (created with the option `{"sharding": "single"}`). EnterpriseGraphs can still be created in a single server deployment, if the sharding option was not set to `single` during the database creation. Affected Versions: 3.12.x Fixed in Versions: - Reference: BTS-1841 (internal)
Date Added: 2024-04-24 Component: arangod Deployment Mode: All Description: ArangoDB uses the ICU library for Unicode handling in version 64 for its core (ArangoSearch, AQL, RocksDB) but version 73 in JavaScript contexts since v3.12.0. If you compare or sort string values with JavaScript and with the core, the values may not match or have a different order. This is due to changes in the Unicode standard and the binary representation of strings for comparisons. You can be affected if you use JavaScript-based features like Foxx microservices or user-defined AQL functions (UDFs), compare or sort strings in them, and Unicode characters for which the standard has changed between the two ICU versions are involved. Affected Versions: 3.12.x Fixed in Versions: - Reference: BTS-1854 (internal)
Date Added: 2024-07-03 Component: arangod Deployment Mode: All Description: ArangoDB can crash if run on bare metal and the Linux distribution uses a different glibc version, the `libnss-` libraries are installed, and the `/etc/nsswitch.conf` configuration file contains settings other than for `files` and `dns` in the `hosts:` line, or the `passwd:` and `group:` lines contain something other than `files`. If you use a fixed version, it can still crash under these circumstances if you enable the `--honor-nsswitch` startup option. Affected Versions:* 3.11.10 (non-hotfix), 3.12.0 Fixed in Versions: 3.11.10-1, 3.12.1 Reference: Incompatibility due to switch to glibc