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.0
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.0-RC.5
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.0-RC.5
Fixed in Versions: -
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.0-RC.5
Fixed in Versions: -
Reference: arangodb/backlog#510 (internal)
Date Added: 2018-12-03
Component: ArangoSearch
Deployment Mode: All
Description: ArangoSearch index format included starting from 3.4.0-RC.4 is incompatible to earlier released 3.4.0 release candidates. Dump and restore is needed when upgrading from 3.4.0-RC.4 to a newer 3.4.0.x release
Affected Versions: 3.4.0-RC.5
Fixed in Versions: -
Reference: N/A
Date Added: 2018-12-03
Component: ArangoSearch
Deployment Mode: All
Description: RocksDB recovery fails sometimes after renaming a view
Affected Versions: 3.4.0-RC.5
Fixed in Versions: -
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.0-RC.5
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.0-RC.5
Fixed in Versions: -
Reference: arangodb/backlog#316 (internal)
Date Added: 2018-12-03
Component: ArangoSearch
Deployment Mode: All
Description: ArangoSearch index format included starting from 3.4.0-RC.3 is incompatible to earlier released 3.4.0 release candidates. Dump and restore is needed when upgrading from 3.4.0-RC.2 to a newer 3.4.0.x release
Affected Versions: 3.4.0-RC.5
Fixed in Versions: -
Reference: N/A
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.0
Fixed in Versions: -
Reference: N/A

Upgrading

Issue
Date Added: 2019-05-16
Component: ArangoSearch
Deployment Mode: All
Description: Upgrading ArangoSearch Views from 3.4.x to 3.5.0 pre-releases is not supported for the time being. You may recreate them manually however. If the server encounters views in an upgrade, it will fail with the following message:
FATAL [7db7c] {arangosearch} Upgrading views is not supported in 3.5RC1, please drop all the existing views and manually recreate them after the upgrade is complete
Affected Versions: 3.5.0-RC.x
Fixed in Versions: -
Reference: N/A
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 (Windows and Linux)
Fixed in Versions: -
Reference: arangodb/planning#3745 (internal)

Stream Transactions

Issue
Date Added: 2019-08-19
Component: Transactions
Deployment Mode: All
Description: Stream Transactions currently 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. It is planned to add the enforcements of the limits with ArangoDB 3.5.1.
Affected Versions: 3.5.0 RC1 to 3.5.0 (including)
Fixed in Versions: -
Reference: N/A
Date Added: 2019-08-19
Component: Transactions
Deployment Mode: All
Description: Stream Transactions currently do not support the graph operations that are initiated via the general-graph JavaScript module or via the REST API at /_api/gharial. Right now these operations will act as if no stream transaction is present. Stream transaction support for these operations will be added later.
Affected Versions: 3.5.0 RC1 to 3.5.0 (including)
Fixed in Versions: -
Reference: N/A
Date Added: 2019-08-19
Component: Transactions
Deployment Mode: All
Description: Stream Transactions currently do not support user restrictions. Any authenticated user may access any ongoing transaction so long as they have access to the database in question. A fix for this is forthcoming.
Affected Versions: 3.5.0 RC1 to 3.5.0 (including)
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.
Affected Versions: 3.5.0-RC.x
Fixed in Versions: -
Reference: N/A
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.0-RC.x
Fixed in Versions: -
Reference: N/A
Date Added: 2019-05-24
Component: Web UI
Deployment Mode: All
Description: The LOGS menu entry in the web interface does not work.
Affected Versions: 3.5.0-RC.x
Fixed in Versions: -
Reference: N/A