Known Issues in ArangoDB 3.7

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

    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, , 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
    Fixed in Versions: -
    Reference:
    Date Added: 2020-07-22
    Component: AQL
    Deployment Mode: Cluster
    Description: When explicitly destroying an AQL Cursor created with stream: true in a cluster deployment, the server does not reply (the request hangs forever).
    Affected Versions: 3.6.x, 3.7.0
    Fixed in Versions: 3.7.1
    Reference: BTS-126 (internal)
    Date Added: 2021-03-24
    Component: AQL
    Deployment Mode: All
    Description: Queries can crash the server if the splice-subqueries optimization is applied and a sub-query has no results. Disabling said optimization via the query option { “optimizer”: { “rules”: [ “-splice-subqueries” ] } } avoids the problem.
    Affected Versions: 3.7.6 - 3.7.10
    Fixed in Versions: 3.7.11
    Reference:
    Date Added: 2021-04-19
    Component: AQL
    Deployment Mode: All
    Description: User-defined variable names in AQL cannot start with an underscore, in contrast to what the AQL documentation claimed.
    Affected Versions: 3.5.x, 3.6.x, 3.7.x, 3.8.x
    Fixed in Versions: 3.9.0
    Reference: arangodb/arangodb#13513
    Date Added: 2021-05-25
    Component: AQL
    Deployment Mode: All
    Description: Global and per-query memory limits are not enforced for AQL graph traversals. Such queries may thus cause out-of-memory issues as they will not be killed despite exceeding the configured —query.memory-limit or Cursor API memoryLimit.
    Affected Versions: 3.5.x, 3.6.x, 3.7.x, 3.8.x, 3.9.x
    Fixed in Versions: -
    Reference: (internal)

    Hot Backup

    Issue
    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, 3.6.x, 3.7.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, 3.6.x, 3.7.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, 3.6.x, 3.7.x
    Fixed in Versions: -
    Reference: N/A
    Date Added: 2021-08-06
    Component: Coordinator
    Deployment Mode: Cluster
    Description: Restoring a hot backup to another deployment that has databases with the same names as in the backup can cause these databases to become inaccessible on Coordinators. They can be listed with db._databases() in arangosh, but not accessed using db._useDatabase().
    Affected Versions: 3.6.x, 3.7.x, 3.8.x
    Fixed in Versions: 3.7.14, 3.8.1
    Reference: (internal)

    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 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-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, 3.6.x, 3.7.x
    Fixed in Versions: -
    Reference: N/A
    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
    Fixed in Versions: -
    Reference: N/A
    Date Added: 2020-04-23
    Component: arangod
    Deployment Mode: Cluster
    Description: The creation of example graphs fails if —cluster.min-replication-factor is set to a value greater than 1, because the system attempts to create the collections with a replication factor of 1 despite the higher minimum.
    Affected Versions: 3.6.x, 3.7.0, 3.7.0-1
    Fixed in Versions: 3.6.4, 3.7.1-alpha.1
    Reference:
    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
    Date Added: 2020-06-30
    Component: SmartGraphs
    Deployment Mode: Cluster
    Description: Changing the collection properties of a smart edge collection did not propagate the changes to child collections for the waitForSync, cacheEnabled and schema attributes. This has been fixed in 3.7.1 for new smart edge collections, created with 3.7.1 or later.
    Affected Versions: 3.4.x, 3.5.x, 3.6.x, 3.7.x
    Fixed in Versions: 3.7.1
    Reference: arangodb/arangodb#12065
    Date Added: 2020-07-31
    Component: Web UI
    Deployment Mode: All
    Description: The API tab of Foxx services does not render the Swagger UI interface.
    Affected Versions: 3.6.x, 3.7.x
    Fixed in Versions: 3.6.6, 3.7.1
    Reference:
    Date Added: 2020-07-31
    Component: Web UI
    Deployment Mode: All
    Description: The web interface confirms the creation of an index, but then displays an error 404: Not Found despite of a successful index creation.
    Affected Versions: 3.6.x, 3.7.x
    Fixed in Versions: 3.6.6, 3.7.1
    Reference: arangodb/arangodb#12248
    Date Added: 2020-07-31
    Component: arangosync
    Deployment Mode: DC2DC
    Description: No JWT rotation takes place with the included arangosync (v0.7.8). If ArangoDB rotates the JWT secret, arangosync processes must be restarted (with the new JWT secret for ArangoDB) if datacenter to datacenter replication is required. That may trigger full resync.
    Affected Versions: 3.7.x
    Fixed in Versions: 3.6.6, 3.7.2
    Reference: N/A
    Date Added: 2020-07-31
    Component: ArangoDB Starter
    Deployment Mode: All
    Description: The included ArangoDB Starter version does not support JWT secret rotation. In addition, there is no way to set the arangod option server.jwt-secret-keyfile (via option pass-through capability of the Starter) because the Starter either ignores it (if no —auth.jwt-secret was used) or blocks it with an error (Pass through option —server.jwt-secret-keyfile conflicts with automatically generated option with value).
    Affected Versions: 3.7.x
    Fixed in Versions: -
    Reference: (internal)
    Date Added: 2020-07-31
    Component: arangosync
    Deployment Mode: DC2DC
    Description: A OneShard cluster deployment can currently not be combined with datacenter to datacenter replication.
    Affected Versions: 3.6.x, 3.7.x
    Fixed in Versions: -
    Reference: N/A
    Date Added: 2020-11-20
    Component: arangod
    Deployment Mode: All
    Description: The value of the startup option —network.io-threads is clamped to 1.
    Affected Versions: 3.6.x, 3.7.x
    Fixed in Versions: 3.6.10, 3.7.5
    Reference: arangodb/arangodb#13051
    Date Added: 2020-11-20
    Component: arangod
    Deployment Mode: All
    Description: The Www-Authenticate header is not set for HTTP 401 responses as required by the HTTP specification, despite the documentation claiming this behavior.
    Affected Versions: 3.5.x, 3.6.x, 3.7.x
    Fixed in Versions: 3.8.0
    Reference:
    Date Added: 2020-12-10
    Component: arangod
    Deployment Mode: Cluster
    Description: A database not found error may occur in a setup with multiple Coordinators when the list of slow queries is accessed or cleared directly after a new database has been created.
    Affected Versions: 3.6.10, 3.7.5
    Fixed in Versions: 3.6.11, 3.7.6
    Reference: arangodb/arangodb#13190
    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
    Fixed in Versions: -
    Reference:
    Date Added: 2021-07-20
    Component: Replication
    Deployment Mode: Cluster
    Description: The synchronous replication protocol used in cluster deployments has a flaw that can cause follower shards to lag behind the leader shards for extended periods of time, without detecting that the synchronization is delayed. While uncommon to occur, it can lead to inconsistencies between replicas that may cause follow-up issues. It is important to upgrade 3.6.x deployments to at least 3.6.15 and 3.7.x deployments to 3.7.13 and to set and keep the supervision in maintenance mode during the whole upgrade process in case of manual cluster deployments. For ArangoDB Starter cluster deployments, make sure to use at least version 0.15.0-1 of the starter. In case of Kubernetes-operated clusters, make sure to use at least version 1.2.0 of kube-arangodb.
    Affected Versions: 3.6.x, 3.7.x
    Fixed in Versions: 3.6.15, 3.7.13
    Reference: Technical Alert #6