Known Issues in ArangoDB 3.5

This page lists important issues affecting the 3.5.x versions of the ArangoDB suite of products. It is not a list of all open issues.

Critical issues (ArangoDB Technical & Security Alerts) are also found at arangodb.com/alerts.

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
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
Fixed in Versions: -
Reference: arangodb/backlog#508 (internal)
Date Added: 2018-12-03
Component: ArangoSearch
Deployment Mode: Cluster
Description: ArangoSearch index consolidation does not work during creation of a link on existing collection which may lead to massive file descriptors consumption
Affected Versions: 3.4.x, 3.5.x
Fixed in Versions: -
Reference: arangodb/backlog#509 (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
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 can not 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
Fixed in Versions: -
Reference: N/A
Date Added: 2019-11-06
Component: ArangoSearch
Deployment Mode: Cluster
Description: There is a possibility to get into deadlocks during Coordinator execution if a custom Analyzer was created (and is present in the _analyzers system collection). It is recommended not to use custom Analyzers in production environments in affected versions.
Affected Versions: 3.5.x
Fixed in Versions: -
Reference: arangodb/backlog#651 (internal)

AQL

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
Fixed in Versions: -
Reference: arangodb/arangodb#6399

Upgrading

Issue
Date Added: 2019-05-16
Component: arangod
Deployment Mode: All
Description: Major upgrades such as 3.3.22 to 3.4.5 fail to upgrade the database directory under CentOS. The server log suggests to use the script /etc/init.d/arangodb but it is not available under CentOS. Workaround: Add database.auto-upgrade = true to /etc/arangodb3/arangod.conf, restart the service, remove database.auto-upgrade = true from the configuration and restart the service once more.
Affected Versions: 3.x.x (CentOS only)
Fixed in Versions: -
Reference: arangodb/release-qa#50 (internal)
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 (Windows and Linux)
Fixed in Versions: -
Reference: arangodb/planning#3745 (internal)
Date Added: 2019-11-06
Component: arangod
Deployment Mode: All
Description: Upgrades from ArangoDB version 3.4.x to 3.5.0 or 3.5.1 don’t create the _analyzers system collection, preventing creation and use of custom Analyzers.
Suggested workaround: Create the missing collection manually in each database of an ArangoDB deployment after upgrade (arangosh example: db._create("_analyzers", {isSystem: true}))
Affected Versions: 3.5.0, 3.5.1
Fixed in Versions: 3.5.2
Reference: arangodb/backlog#652 (internal)
Date Added: 2019-11-06
Component: arangod
Deployment Mode: Cluster
Description: Rolling cluster upgrades from ArangoDB version 3.5.0 to 3.5.1 are not possible due to errors at DBServer nodes. A fix is contained from version 3.5.2 on, and rolling upgrades to this version are possible.
Affected Versions: 3.5.0, 3.5.1
Fixed in Versions: 3.5.2
Reference: arangodb/backlog#652 (internal)

Stream Transactions

Issue
Date Added: 2019-08-19
Component: Transactions
Deployment Mode: All
Description: Stream Transactions do not honor the limits described in the documentation. Currently the idle timeout of 10 seconds will not be enforced, neither will the maximum size of transaction be enforced.
Affected Versions: 3.5.0
Fixed in Versions: 3.5.1
Reference: arangodb/arangodb#9775
Date Added: 2019-08-19
Component: Transactions
Deployment Mode: All
Description: Stream Transactions do not support the graph operations that are initiated via the general-graph / smart-graph JavaScript module or via the REST API at /_api/gharial. These operations will act as if no stream transaction is present.
Affected Versions: 3.5.0
Fixed in Versions: 3.5.1
Reference: arangodb/arangodb#9855 / arangodb/arangodb#9911
Date Added: 2019-08-19
Component: Transactions
Deployment Mode: All
Description: Stream Transactions do not support user restrictions. Any authenticated user may access any ongoing transaction so long as they have access to the database in question.
Affected Versions: 3.5.0
Fixed in Versions: 3.5.1
Reference: arangodb/arangodb#9796

Hot Backup

Issue
Date Added: 2019-10-09
Component: Hot Backup API / arangobackup
Deployment Mode: All
Description: ArangoSearch Views are not backed up and thus not restored yet. Therefore, Views have to be dropped and recreated after a restore. This happens automatically in the background, but in particular in the presence of large amounts of data, the recreation of the ArangoSearch indexes can take some time after the restore. It is planned to rectify this limitation in one of the next releases.
Note furthermore that a running query with views can prevent a restore operation from happening whilst the query is running.
Affected Versions: 3.5.x
Fixed in Versions: -
Reference: N/A
Date Added: 2019-10-09
Component: Hot Backup API / arangobackup
Deployment Mode: All
Description: The Hot Backup feature is not supported in the Windows version of ArangoDB at this point in time.
Affected Versions: 3.5.x
Fixed in Versions: -
Reference: N/A
Date Added: 2019-10-09
Component: Hot Backup API / arangobackup
Deployment Mode: DC2DC
Description: Hot Backup functionality in Datacenter to Datacenter Replication setups is experimental and may not work.
Affected Versions: 3.5.x
Fixed in Versions: -
Reference: N/A
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
Fixed in Versions: -
Reference: N/A

Other

Issue
Date Added: 2019-05-16
Component: Starter
Deployment Mode: All
Description: The ArangoDB Starter falls back to the IP [::1] under macOS. If there is no entry ::1 localhost in the /etc/hosts file or the option --starter.disable-ipv6 is passed to the starter to use IPv4, then it will hang during startup.
Affected Versions: 0.14.3 (macOS only)
Fixed in Versions: -
Reference: N/A
Date Added: 2019-05-16
Component: arangod
Deployment Mode: All
Description: Calling a shutdown endpoint may not result in a proper shutdown while the node/server is still under load. The server processes must be ended manually.
In v3.5.1 and later, two different issues are fixed: libgcc/libmusl wrongly detecting multi-threadedness in statically linked executables and a read/write lock race condition.
Affected Versions: 3.5.0
Fixed in Versions: 3.5.1
Reference: v3.5.1 CHANGELOG / Blog Post “When Exceptions Collide”
Date Added: 2019-05-24
Component: Web UI
Deployment Mode: Active Failover
Description: The web interface shows a wrong replication mode in the replication tab in Active Failover deployments sometimes. It may display Master/Slave mode (the default value) because of timeouts if /_api/cluster/endpoints is requested too frequently.
Affected Versions: 3.5.x
Fixed in Versions: -
Reference: N/A
Date Added: 2019-09-11
Component: Indexing
Deployment Mode: All
Description: A time to live (TTL) index does not remove documents from a collection if the path points to a nested attribute. Only top-level attributes work.
Affected Versions: 3.5.x
Fixed in Versions: -
Reference: N/A