8000 Add --server.allow-deprecated-storage-engine by Simran-B · Pull Request #329 · arangodb/docs · GitHub
[go: up one dir, main page]
Skip to content
This repository was archived by the owner on Dec 13, 2023. It is now read-only.

Add --server.allow-deprecated-storage-engine #329

Closed
wants to merge 2 commits into from
Closed

Add --server.allow-deprecated-storage-engine #329

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
29111d6
Add --server.allow-deprecated-storage-engine
Simran-B Feb 3, 2020
625bd9c
Fix link
Simran-B Feb 3, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Add --server.allow-deprecated-storage-engine
  • Loading branch information
@Simran-B
Simran-B committed Feb 3, 2020
commit 29111d68de9849778128ed336aa2c930f1d70a15
8 changes: 7 additions & 1 deletion 3.7/programs-arangod-server.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,7 +161,13 @@ Since ArangoDB v3.2.0, an alternative engine based on
turned on manually. Since ArangoDB v3.4.0, the RocksDB storage engine is the
default storage engine for new installations.

The MMFiles engine is [deprecated](appendix-deprecated.html) from v3.6.0 on.
The MMFiles engine is [deprecated](appendix-deprecated.html) from v3.6.0 on
and new deployments created with v3.7 do not allow MMFiles as storage engine
anymore unless the startup option `--server.allow-deprecated-storage-engine`
is set to *true*. Deployments upgraded to v3.7 from earlier versions that are
using the MMFiles storage engine will still continue to work in ArangoDB 3.7.
However, 3.7 will be the last ArangoDB version supporting the MMFiles storage
engines, so users are asked to migrate to the RocksDB storage engine soon.

One storage engine type is supported per server per installation.
Live switching of storage engines on already installed systems isn't supported.
Expand Down
23 changes: 13 additions & 10 deletions 3.7/release-notes-upgrading-changes37.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,16 +14,19 @@ MMFiles storage engine
----------------------

This version of ArangoDB does not allow creating any new deployments with the
MMFiles storage engine. All storage engine selection functionality has been removed
from the ArangoDB package installers. The RocksDB storage engine will be selected
for any new deployments created with ArangoDB 3.7.
The RocksDB storage engine is the default storage engine since ArangoDB 3.4, and
the MMFiles storage engine has been deprecated in ArangoDB 3.6.

Deployments upgrading from ArangoDB 3.6 that are using the MMFiles storage engine
will still continue to work in ArangoDB 3.7. However, 3.7 will be the last ArangoDB
version supporting the MMFiles storage engines, so users are asked to migrate to the
RocksDB storage engine soon.
MMFiles storage engine, unless the new [startup option](programs-arangod-server.html#allow-deprecated-storage-engine)
`--server.allow-deprecated-storage-engine` is set to *true*.

All storage engine selection functionality has been removed from the ArangoDB
package installers. The RocksDB storage engine will be selected for any new
deployments created with ArangoDB 3.7 by default. The RocksDB storage engine is
the default storage engine since ArangoDB 3.4, and the MMFiles storage engine
has been deprecated in ArangoDB 3.6.

Deployments upgrading from ArangoDB 3.6 that are using the MMFiles storage
engine will still continue to work in ArangoDB 3.7. However, 3.7 will be the
last ArangoDB version supporting the MMFiles storage engines, so users are
asked to migrate to the RocksDB storage engine soon.

HTTP REST API
-------------
Expand Down
0