ArangoDB v3.8 reached End of Life (EOL) and is no longer supported.
This documentation is outdated. Please see the most recent version at docs.arangodb.com
Known Issues in ArangoDB 3.3
This page lists important issues affecting the 3.3.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.
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.3.x (all) Fixed in Versions: - Reference: arangodb/arangodb#5342 |
Date Added: 2018-11-30 Component: arangod Deployment Mode: All Description: Wrong suggestion printed in the log on how to optimize an OS setting, if followed, could cause ArangoDB to run into problems as the number of memory mappings will keep growing Affected Versions: 3.3.0 to 3.3.19 Fixed in Versions: 3.3.20 Reference: https://www.arangodb.com/alerts/tech03/ |
Date Added: 2018-11-16 Component: Backup/Restore Deployment Mode: All Description: Users not included in the backup if --server.authentication = true Affected Versions: 3.3.0 to 3.3.13 Fixed in Versions: 3.3.14 Reference: https://www.arangodb.com/alerts/tech02/ |
Date Added: 2018-11-03 Component: Security Deployment Mode: All Description: Unauthorized access to ArangoDB when using LDAP authentication Affected Versions: 3.3.0 to 3.3.18 Fixed in Versions: 3.3.19 Reference: https://www.arangodb.com/alerts/sec01/ |
Date Added: 2018-04-09 Component: Storage Deployment Mode: Single Instance Description: Data corruption could happen under Linux Affected Versions: 3.3.0 Fixed in Versions: 3.3.1 Reference: https://www.arangodb.com/alerts/tech01/ |
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: all 3.x versions (Windows only) Fixed in Versions: 3.3.23, 3.4.4 Reference: facebook/rocksdb#4983 |
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 Fixed in Versions: 3.3.24, 3.4.7 Reference: arangodb/arangodb#9404 |