Technical Alert #1: Important Note for Users running ArangoDB v. 3.2.4, 3.2.5, 3.2.6, 3.2.7, 3.2.8, 3.2.9 or 3.3.0 on Linux
Last year, ArangoDB had a log data storage bug in versions from 3.2.4 to 3.2.9 and in version 3.3.0.
After receiving reports from our Community we investigated and fixed the bug. A fix was released on December 22 2017, with v. 3.2.10, and on December 28 2017, v. 3.3.1.
If you believe you are affected by this bug, we would highly recommend to upgrade your ArangoDB instances to the latest version of the respective ArangoDB series as soon as possible.
Am I affected by the log data storage bug?
You are affected if you meet all of the following criteria:
- You are running ArangoDB from v. 3.2.4 to v. 3.2.9 (included), or v. 3.3.0.
- You are running ArangoDB on a Linux Distribution.
- You have installed ArangoDB with the automatic installer delivered with the official binaries.
- You are running a single instance of ArangoDB.
If you are running v. 3.2.10 or later, or v. 3.3.1 or later, or running ArangoDB in Cluster mode you are not affected. You are also not affected if you installed ArangoDB manually or with the tool ArangoDB Starter.
What does the log data storage bug do?
ArangoDB creates log files and writes to them. In case the log files exceed a certain size, the files are compressed, moved to a new folder, and on the same address a new log file is created.
Caused by a mistake in the build process of the ArangoDB packages, the bug caused log data to not be written to the newly generated log file. Instead, data was being written to a random file, which could cause data corruption.
What do I have to do?
If you are affected, we highly recommend to create a backup of your data using the tool arangodump and then upgrade to the latest version of the respective ArangoDB 3.2 or 3.3 series.