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.

ArangoDB Customers can access the Technical & Security Alerts page after login into the Support Portal.

# Issue
5 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
4 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: Link for ArangoDB Customers
3 Date Added: 2018-11-16
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: Link for ArangoDB Customers
2 Date Added: 2018-11-03
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: Link for ArangoDB Customers
1 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: Link for ArangoDB Customers