From 1ddd5cef7be37cd9e94e8913470248d6b5db9ebe Mon Sep 17 00:00:00 2001 From: Simran Spiller Date: Thu, 11 Dec 2025 15:35:54 +0100 Subject: [PATCH 1/2] Add known issue: Partitioning RocksDB files for documents can create many small files --- .../3.12/release-notes/version-3.12/known-issues-in-3-12.md | 1 + .../4.0/release-notes/version-3.12/known-issues-in-3-12.md | 1 + 2 files changed, 2 insertions(+) diff --git a/site/content/arangodb/3.12/release-notes/version-3.12/known-issues-in-3-12.md b/site/content/arangodb/3.12/release-notes/version-3.12/known-issues-in-3-12.md index c09b1ae18c..4efb9272c6 100644 --- a/site/content/arangodb/3.12/release-notes/version-3.12/known-issues-in-3-12.md +++ b/site/content/arangodb/3.12/release-notes/version-3.12/known-issues-in-3-12.md @@ -51,3 +51,4 @@ Note that this page does not list all open issues. | **Date Added:** 2024-07-03
**Component:** arangod
**Deployment Mode:** All
**Description:** ArangoDB can crash if run on bare metal and the Linux distribution uses a different glibc version, the `libnss-*` libraries are installed, and the `/etc/nsswitch.conf` configuration file contains settings other than for `files` and `dns` in the `hosts:` line, or the `passwd:` and `group:` lines contain something other than `files`. If you use a fixed version, it can still crash under these circumstances if you enable the `--honor-nsswitch` startup option.
**Affected Versions:** 3.11.10 (non-hotfix), 3.12.0
**Fixed in Versions:** 3.11.10-1, 3.12.1
**Reference:** [Incompatibility due to switch to glibc](incompatible-changes-in-3-12.md#incompatibilities-due-to-switch-to-glibc) | | **Date Added:** 2025-01-30
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** If the invariant is violated that ArangoDB's data is not modified while a server is down, manually as well as automatically triggered operations such as moving shards can make a DB-Server the leader (again) even though it may not have the correct data. ArangoDB does currently not protect against certain cases like bringing a DB-Server back without data (by accident or on purpose), which can lead to this empty state getting replicated across the cluster and thus causing data loss.
**Affected Versions:** 3.11.x, 3.12.x
**Fixed in Versions:** -
**Reference:** N/A | | **Date Added:** 2025-06-25
**Component:** Web interface
**Deployment Mode:** All
**Description:** Specifying an `X-Script-Name` HTTP header in requests to the web interface (`/_admin/aardvark`) to add a path prefix is non-functional. The feature was originally added in version 3.0 for basic proxy setups but doesn't adequately handle the requests of certain internal services.
**Affected Versions:** 3.11.x, 3.12.x
**Fixed in Versions:** -
**Reference:** N/A | +| **Date Added:** 2025-12-11
**Component:** arangod
**Deployment Mode:** All
**Description:** The storage engine-related `--rocksdb.partition-files-for-documents` startup option has a default of `true` since v3.12.6, causing RocksDB to use separate `.sst` files for every collection/shard to store document data. This can create a very large number of files and use the same amount of file descriptors for deployments with many collections/shards and a high write load. It is recommended to disable the feature with `--rocksdb.partition-files-for-documents false` in versions where it is enabled by default.
**Affected Versions:** 3.12.6, 3.12.7
**Fixed in Versions:** 3.12.8
**Reference:** [arangodb/arangodb#22181](https://github.com/arangodb/arangodb/pull/22181) | diff --git a/site/content/arangodb/4.0/release-notes/version-3.12/known-issues-in-3-12.md b/site/content/arangodb/4.0/release-notes/version-3.12/known-issues-in-3-12.md index c09b1ae18c..4efb9272c6 100644 --- a/site/content/arangodb/4.0/release-notes/version-3.12/known-issues-in-3-12.md +++ b/site/content/arangodb/4.0/release-notes/version-3.12/known-issues-in-3-12.md @@ -51,3 +51,4 @@ Note that this page does not list all open issues. | **Date Added:** 2024-07-03
**Component:** arangod
**Deployment Mode:** All
**Description:** ArangoDB can crash if run on bare metal and the Linux distribution uses a different glibc version, the `libnss-*` libraries are installed, and the `/etc/nsswitch.conf` configuration file contains settings other than for `files` and `dns` in the `hosts:` line, or the `passwd:` and `group:` lines contain something other than `files`. If you use a fixed version, it can still crash under these circumstances if you enable the `--honor-nsswitch` startup option.
**Affected Versions:** 3.11.10 (non-hotfix), 3.12.0
**Fixed in Versions:** 3.11.10-1, 3.12.1
**Reference:** [Incompatibility due to switch to glibc](incompatible-changes-in-3-12.md#incompatibilities-due-to-switch-to-glibc) | | **Date Added:** 2025-01-30
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** If the invariant is violated that ArangoDB's data is not modified while a server is down, manually as well as automatically triggered operations such as moving shards can make a DB-Server the leader (again) even though it may not have the correct data. ArangoDB does currently not protect against certain cases like bringing a DB-Server back without data (by accident or on purpose), which can lead to this empty state getting replicated across the cluster and thus causing data loss.
**Affected Versions:** 3.11.x, 3.12.x
**Fixed in Versions:** -
**Reference:** N/A | | **Date Added:** 2025-06-25
**Component:** Web interface
**Deployment Mode:** All
**Description:** Specifying an `X-Script-Name` HTTP header in requests to the web interface (`/_admin/aardvark`) to add a path prefix is non-functional. The feature was originally added in version 3.0 for basic proxy setups but doesn't adequately handle the requests of certain internal services.
**Affected Versions:** 3.11.x, 3.12.x
**Fixed in Versions:** -
**Reference:** N/A | +| **Date Added:** 2025-12-11
**Component:** arangod
**Deployment Mode:** All
**Description:** The storage engine-related `--rocksdb.partition-files-for-documents` startup option has a default of `true` since v3.12.6, causing RocksDB to use separate `.sst` files for every collection/shard to store document data. This can create a very large number of files and use the same amount of file descriptors for deployments with many collections/shards and a high write load. It is recommended to disable the feature with `--rocksdb.partition-files-for-documents false` in versions where it is enabled by default.
**Affected Versions:** 3.12.6, 3.12.7
**Fixed in Versions:** 3.12.8
**Reference:** [arangodb/arangodb#22181](https://github.com/arangodb/arangodb/pull/22181) | From 91bc7c4221464c63780b5583e61cade2e2c7cf2f Mon Sep 17 00:00:00 2001 From: Simran Spiller Date: Wed, 17 Dec 2025 11:26:54 +0100 Subject: [PATCH 2/2] Update version info and add remark to incompatible changes --- .../version-3.12/incompatible-changes-in-3-12.md | 15 ++++++++++++++- .../version-3.12/known-issues-in-3-12.md | 2 +- .../version-3.12/incompatible-changes-in-3-12.md | 15 ++++++++++++++- .../version-3.12/known-issues-in-3-12.md | 2 +- 4 files changed, 30 insertions(+), 4 deletions(-) diff --git a/site/content/arangodb/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md b/site/content/arangodb/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md index 959cea82cf..cb3a2483fb 100644 --- a/site/content/arangodb/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md +++ b/site/content/arangodb/3.12/release-notes/version-3.12/incompatible-changes-in-3-12.md @@ -920,8 +920,21 @@ RocksDB-related startup options have been changed: - `--rocksdb.pending-compactions-slowdown-trigger` has been changed from 128 KiB to 1 GiB. - `--rocksdb.pending-compactions-stop-trigger` has been changed from 16 GiB to 32 GiB. -- `--rocksdb.partition-files-for-documents` has been changed from false to true. - `--rocksdb.throttle-slow-down-writes-trigger` has been obsoleted. +- `--rocksdb.partition-files-for-documents` has been changed from false to true. + +{{< warning >}} +If the `--rocksdb.partition-files-for-documents` startup option is enabled, it +causes RocksDB to use separate `.sst` files for every collection/shard to store +document data. This can create a very large number of files and use the same +amount of file descriptors for deployments with many collections/shards and a +high write load. + +It is recommended to disable the feature explicitly with +`--rocksdb.partition-files-for-documents false` in versions from 3.12.6 through +3.12.7 where it is enabled by default. From 3.12.7-1 and 3.12.8 onward, it is +again disabled by default. +{{< /warning >}} ## Optional elevation for GeoJSON Points diff --git a/site/content/arangodb/3.12/release-notes/version-3.12/known-issues-in-3-12.md b/site/content/arangodb/3.12/release-notes/version-3.12/known-issues-in-3-12.md index 4efb9272c6..e70b6e20a5 100644 --- a/site/content/arangodb/3.12/release-notes/version-3.12/known-issues-in-3-12.md +++ b/site/content/arangodb/3.12/release-notes/version-3.12/known-issues-in-3-12.md @@ -51,4 +51,4 @@ Note that this page does not list all open issues. | **Date Added:** 2024-07-03
**Component:** arangod
**Deployment Mode:** All
**Description:** ArangoDB can crash if run on bare metal and the Linux distribution uses a different glibc version, the `libnss-*` libraries are installed, and the `/etc/nsswitch.conf` configuration file contains settings other than for `files` and `dns` in the `hosts:` line, or the `passwd:` and `group:` lines contain something other than `files`. If you use a fixed version, it can still crash under these circumstances if you enable the `--honor-nsswitch` startup option.
**Affected Versions:** 3.11.10 (non-hotfix), 3.12.0
**Fixed in Versions:** 3.11.10-1, 3.12.1
**Reference:** [Incompatibility due to switch to glibc](incompatible-changes-in-3-12.md#incompatibilities-due-to-switch-to-glibc) | | **Date Added:** 2025-01-30
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** If the invariant is violated that ArangoDB's data is not modified while a server is down, manually as well as automatically triggered operations such as moving shards can make a DB-Server the leader (again) even though it may not have the correct data. ArangoDB does currently not protect against certain cases like bringing a DB-Server back without data (by accident or on purpose), which can lead to this empty state getting replicated across the cluster and thus causing data loss.
**Affected Versions:** 3.11.x, 3.12.x
**Fixed in Versions:** -
**Reference:** N/A | | **Date Added:** 2025-06-25
**Component:** Web interface
**Deployment Mode:** All
**Description:** Specifying an `X-Script-Name` HTTP header in requests to the web interface (`/_admin/aardvark`) to add a path prefix is non-functional. The feature was originally added in version 3.0 for basic proxy setups but doesn't adequately handle the requests of certain internal services.
**Affected Versions:** 3.11.x, 3.12.x
**Fixed in Versions:** -
**Reference:** N/A | -| **Date Added:** 2025-12-11
**Component:** arangod
**Deployment Mode:** All
**Description:** The storage engine-related `--rocksdb.partition-files-for-documents` startup option has a default of `true` since v3.12.6, causing RocksDB to use separate `.sst` files for every collection/shard to store document data. This can create a very large number of files and use the same amount of file descriptors for deployments with many collections/shards and a high write load. It is recommended to disable the feature with `--rocksdb.partition-files-for-documents false` in versions where it is enabled by default.
**Affected Versions:** 3.12.6, 3.12.7
**Fixed in Versions:** 3.12.8
**Reference:** [arangodb/arangodb#22181](https://github.com/arangodb/arangodb/pull/22181) | +| **Date Added:** 2025-12-11
**Component:** arangod
**Deployment Mode:** All
**Description:** The storage engine-related `--rocksdb.partition-files-for-documents` startup option has a default of `true` since v3.12.6, causing RocksDB to use separate `.sst` files for every collection/shard to store document data. This can create a very large number of files and use the same amount of file descriptors for deployments with many collections/shards and a high write load. It is recommended to disable the feature with `--rocksdb.partition-files-for-documents false` in versions where it is enabled by default.
**Affected Versions:** 3.12.6 - 3.12.7
**Fixed in Versions:** 3.12.7-1, 3.12.8
**Reference:** [arangodb/arangodb#22181](https://github.com/arangodb/arangodb/pull/22181) | diff --git a/site/content/arangodb/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md b/site/content/arangodb/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md index 959cea82cf..cb3a2483fb 100644 --- a/site/content/arangodb/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md +++ b/site/content/arangodb/4.0/release-notes/version-3.12/incompatible-changes-in-3-12.md @@ -920,8 +920,21 @@ RocksDB-related startup options have been changed: - `--rocksdb.pending-compactions-slowdown-trigger` has been changed from 128 KiB to 1 GiB. - `--rocksdb.pending-compactions-stop-trigger` has been changed from 16 GiB to 32 GiB. -- `--rocksdb.partition-files-for-documents` has been changed from false to true. - `--rocksdb.throttle-slow-down-writes-trigger` has been obsoleted. +- `--rocksdb.partition-files-for-documents` has been changed from false to true. + +{{< warning >}} +If the `--rocksdb.partition-files-for-documents` startup option is enabled, it +causes RocksDB to use separate `.sst` files for every collection/shard to store +document data. This can create a very large number of files and use the same +amount of file descriptors for deployments with many collections/shards and a +high write load. + +It is recommended to disable the feature explicitly with +`--rocksdb.partition-files-for-documents false` in versions from 3.12.6 through +3.12.7 where it is enabled by default. From 3.12.7-1 and 3.12.8 onward, it is +again disabled by default. +{{< /warning >}} ## Optional elevation for GeoJSON Points diff --git a/site/content/arangodb/4.0/release-notes/version-3.12/known-issues-in-3-12.md b/site/content/arangodb/4.0/release-notes/version-3.12/known-issues-in-3-12.md index 4efb9272c6..e70b6e20a5 100644 --- a/site/content/arangodb/4.0/release-notes/version-3.12/known-issues-in-3-12.md +++ b/site/content/arangodb/4.0/release-notes/version-3.12/known-issues-in-3-12.md @@ -51,4 +51,4 @@ Note that this page does not list all open issues. | **Date Added:** 2024-07-03
**Component:** arangod
**Deployment Mode:** All
**Description:** ArangoDB can crash if run on bare metal and the Linux distribution uses a different glibc version, the `libnss-*` libraries are installed, and the `/etc/nsswitch.conf` configuration file contains settings other than for `files` and `dns` in the `hosts:` line, or the `passwd:` and `group:` lines contain something other than `files`. If you use a fixed version, it can still crash under these circumstances if you enable the `--honor-nsswitch` startup option.
**Affected Versions:** 3.11.10 (non-hotfix), 3.12.0
**Fixed in Versions:** 3.11.10-1, 3.12.1
**Reference:** [Incompatibility due to switch to glibc](incompatible-changes-in-3-12.md#incompatibilities-due-to-switch-to-glibc) | | **Date Added:** 2025-01-30
**Component:** arangod
**Deployment Mode:** Cluster
**Description:** If the invariant is violated that ArangoDB's data is not modified while a server is down, manually as well as automatically triggered operations such as moving shards can make a DB-Server the leader (again) even though it may not have the correct data. ArangoDB does currently not protect against certain cases like bringing a DB-Server back without data (by accident or on purpose), which can lead to this empty state getting replicated across the cluster and thus causing data loss.
**Affected Versions:** 3.11.x, 3.12.x
**Fixed in Versions:** -
**Reference:** N/A | | **Date Added:** 2025-06-25
**Component:** Web interface
**Deployment Mode:** All
**Description:** Specifying an `X-Script-Name` HTTP header in requests to the web interface (`/_admin/aardvark`) to add a path prefix is non-functional. The feature was originally added in version 3.0 for basic proxy setups but doesn't adequately handle the requests of certain internal services.
**Affected Versions:** 3.11.x, 3.12.x
**Fixed in Versions:** -
**Reference:** N/A | -| **Date Added:** 2025-12-11
**Component:** arangod
**Deployment Mode:** All
**Description:** The storage engine-related `--rocksdb.partition-files-for-documents` startup option has a default of `true` since v3.12.6, causing RocksDB to use separate `.sst` files for every collection/shard to store document data. This can create a very large number of files and use the same amount of file descriptors for deployments with many collections/shards and a high write load. It is recommended to disable the feature with `--rocksdb.partition-files-for-documents false` in versions where it is enabled by default.
**Affected Versions:** 3.12.6, 3.12.7
**Fixed in Versions:** 3.12.8
**Reference:** [arangodb/arangodb#22181](https://github.com/arangodb/arangodb/pull/22181) | +| **Date Added:** 2025-12-11
**Component:** arangod
**Deployment Mode:** All
**Description:** The storage engine-related `--rocksdb.partition-files-for-documents` startup option has a default of `true` since v3.12.6, causing RocksDB to use separate `.sst` files for every collection/shard to store document data. This can create a very large number of files and use the same amount of file descriptors for deployments with many collections/shards and a high write load. It is recommended to disable the feature with `--rocksdb.partition-files-for-documents false` in versions where it is enabled by default.
**Affected Versions:** 3.12.6 - 3.12.7
**Fixed in Versions:** 3.12.7-1, 3.12.8
**Reference:** [arangodb/arangodb#22181](https://github.com/arangodb/arangodb/pull/22181) |