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

Known Issues in ArangoDB 3.4

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

Note that this page does not list all open issues.

ArangoSearch

Issue
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: 3.6.0
Reference: arangodb/backlog#509  (internal)
Date Added: 2018-12-03
Component: ArangoSearch
Deployment Mode: Cluster
Description: Long-running DML transactions on collections (linked with ArangoSearch view) block “ArangoDB flush thread” making impossible to refresh data “visible” by a view
Affected Versions: 3.4.x
Fixed in Versions: 3.5.0
Reference: arangodb/backlog#510  (internal)
Date Added: 2018-12-03
Component: ArangoSearch
Deployment Mode: All
Description: RocksDB recovery fails sometimes after renaming a view
Affected Versions: 3.4.x
Fixed in Versions: 3.5.0
Reference: arangodb/backlog#469  (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: 2018-12-03
Component: ArangoSearch
Deployment Mode: All
Description: Using score functions (BM25/TFIDF) in ArangoDB expression is not supported
Affected Versions: 3.4.x
Fixed in Versions: 3.5.0
Reference: arangodb/backlog#316  (internal)
Date Added: 2019-05-16
Component: ArangoSearch
Deployment Mode: All
Description: You may experience server slowdowns caused by Views. Removing a collection link from the view configuration mitigates the problem.
Affected Versions: 3.4.x, 3.5.x
Fixed in Versions: -
Reference: N/A
Date Added: 2019-05-28
Component: ArangoSearch
Deployment Mode: All
Description: For specific input data indexed by ArangoSearch and used via views functionality a crash can occur during lookup (AQL query execution) in the internal index structure. This issue affects only view-related AQL queries with the SEARCH keyword involved. Please upgrade to ArangoDB v3.4.6 (or newer) which contains a fix for the ArangoSearch implementation and reindex views by recreating them (drop and create with the same parameters).
Affected Versions: 3.4.x
Fixed in Versions: 3.4.6
Reference: N/A

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: Upgrading from 3.4.4 to 3.4.x under CentOS using rpm -U or yum upgrade is unable to succeed because of a problem with the package. The arangodb3 service will not be available anymore. Uninstalling with rpm -e or yum remove may fail or not clean up all of the folders.
Affected Versions: >= 3.4.4
Fixed in Versions: 3.4.8, 3.5.0 (upgrading works from these versions on again)
Reference: arangodb/release-qa#50  (internal)
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.4.x (CentOS only)
Fixed in Versions: 3.4.8
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-12-10
Component: Installer
Deployment Mode: All
Description: The NSIS installer for Windows may fail to upgrade an existing installation, e.g. from 3.4.a to 3.4.b (patch release), with the error message: “failed to detect whether we need to Upgrade”
Affected Versions: 3.4.x
Fixed in Versions: -
Reference: arangodb/release-qa#183  (internal)
Date Added: 2020-01-07
Component: Installer
Deployment Mode: All
Description: The NSIS installer for Windows can fail to add the path to the ArangoDB binaries to the PATH environment variable, silently or with an error.
Affected Versions: 3.4.x
Fixed in Versions: -
Reference: arangodb/release-qa#183  (internal)

Other

Issue
Date Added: 2018-12-04
Component: arangod
Deployment Mode: All
Description: Parallel creation of collections using multiple client connections with the same database user may spuriously fail with “Could not update user due to conflict” warnings when setting user permissions on the new collections. A follow-up effect of this may be that access to the just-created collection is denied.
Affected Versions: 3.4.0
Fixed in Versions: 3.4.1
Reference: arangodb/arangodb#5342 
Date Added: 2019-02-18
Component: arangod
Deployment Mode: All
Description: There is a clock overflow bug within Facebook’s RocksDB storage engine for Windows. The problem manifests under heavy write loads, including long imports. The Windows server will suddenly block all writes for minutes or hours, then begin working again just fine. An immediate workaround is to change the server configuration:
[rocksdb]
throttle = false
Affected Versions: 3.x.x (Windows only)
Fixed in Versions: 3.3.23, 3.4.4
Reference: facebook/rocksdb#4983 
Date Added: 2019-03-13
Component: arangod
Deployment Mode: Active Failover
Description: A full resync is triggered after a failover, when the former leader instance is brought back online. A full resync may even occur twice sporadically.
Affected Versions: all 3.4.x versions
Fixed in Versions: 3.4.5
Reference: arangodb/planning#3757  (internal)
Date Added: 2019-03-13
Component: arangod
Deployment Mode: Active Failover
Description: The leader instance may hang on shutdown. This behavior was observed in an otherwise successful failover.
Affected Versions: all 3.4.x versions
Fixed in Versions: -
Reference: arangodb/planning#3756  (internal)
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-29
Component: Web UI
Deployment Mode: All
Description: The LOGS menu entry in the web interface does not work.
Affected Versions: 3.4.6
Fixed in Versions: 3.4.7
Reference: arangodb/arangodb#9093 
Date Added: 2019-06-04
Component: Agency
Deployment Mode: Cluster
Description: Data loss can occur in the form of collections getting dropped. This may occur for any collection newly created in v3.4.6 clusters.
Affected Versions: 3.4.6
Fixed in Versions: 3.4.6-1
Reference: arangodb.com/alerts/tech05/ 
Date Added: 2019-07-04
Component: Config file parsing
Deployment Mode: All
Description: Config file parser may produce unexpected values for settings that contain comments and a unit modifier.
Affected Versions: 3.x.x
Fixed in Versions: 3.3.24, 3.4.7
Reference: arangodb/arangodb#9404 
Date Added: 2019-09-14
Component: arangod
Deployment Mode: All
Description: The user-provided value to the startup option http.keep-alive-timeout is ignored.
Affected Versions: 3.4.x
Fixed in Versions: 3.5.0
Reference: N/A
Date Added: 2019-12-10
Component: Installer
Deployment Mode: All
Description: The DMG package for macOS is not notarized, which prevents the execution of ArangoDB3-CLI.app under macOS 10.15 (Catalina) with error message: “ArangoDB3-CLI can’t be opened because Apple cannot check it for malicious software”
Affected Versions: 3.3.x, 3.4.x
Fixed in Versions: 3.4.10, 3.5.5, 3.6.1
Reference: arangodb/arangodb#10561 
Date Added: 2020-01-07
Component: Installer
Deployment Mode: All
Description: V8-based binaries of the client packages (arangosh, arangoinspect, foxx-manager) have an incorrect default value for javascript.startup-directory and will thus not find the required JavaScript folder unless specified by the user.
Affected Versions: 3.4.x, 3.5.x, 3.6.0
Fixed in Versions: 3.4.9, 3.5.4, 3.6.1
Reference: arangodb/release-qa#183  (internal)
Date Added: 2020-01-07
Component: Installer
Deployment Mode: All
Description: The client packages for Windows miss the arangoinspect binary. As a workaround, you can run arangosh with the following options:
arangosh --server.authentication false --server.ask-jwt-secret --javascript.client-module inspector.js …
Affected Versions: 3.3.x, 3.4.x, 3.5.x, 3.6.0
Fixed in Versions: 3.3.25, 3.4.10, 3.5.5, 3.6.1
Reference: arangodb/arangodb#10835 
Date Added: 2020-01-07
Component: Foxx
Deployment Mode: Cluster
Description: In case of a Foxxmaster failover, jobs in state 'progress' are not reset to 'pending' to restart execution.
Affected Versions: 3.4.x
Fixed in Versions: 3.4.10, 3.5.5, 3.6.1
Reference: arangodb/arangodb#10800 
Date Added: 2020-05-18
Component: all arangod / arangosh based programs & tools
Deployment Mode: All
Description: When using the --config option to set the configuration file location the ArangoDB C++ binaries check for <filename>.local among other paths. If this path happens to be a directory then the expected configuration cannot be read, resulting in an early exit.
Affected Versions: 3.4.x
Fixed in Versions: 3.4.11
Reference: arangodb/arangodb#11632 
Date Added: 2020-06-19
Component: SmartGraphs
Deployment Mode: Cluster
Description: When inserting edges into an edge collection of a SmartGraph, the auto-generated _rev values for the ingoing and outgoing part of the edge may differ. This can be confusing when querying the _rev values of the edges later.
Affected Versions: 3.4.x, 3.5.x, 3.6.x, 3.7.x
Fixed in Versions: 3.6.5, 3.7.1
Reference: N/A

On this page