Skip to content

Release notes about deprecation of --rocksdb.transaction-lock-timeout startup option #762

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -1075,6 +1075,16 @@ background compactions. The changed default ensures this cleanup to happen more
frequently. Compactions can potentially lead to spikes in CPU, memory, and I/O
usage. You may now observe this daily instead of monthly.

### RocksDB transaction lock timeout controlled internally

<small>Deprecated in: v3.12.6</small>

The `--rocksdb.transaction-lock-timeout` startup option has been deprecated.
It was supposed to let you configure the wait timeout in milliseconds for
locking a document in a transaction. However, the lock timeout is actually set
to differnet values internally, depending on what is a meaningful timeout for
a given case.

## Client tools

### arangodump
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -1075,6 +1075,16 @@ background compactions. The changed default ensures this cleanup to happen more
frequently. Compactions can potentially lead to spikes in CPU, memory, and I/O
usage. You may now observe this daily instead of monthly.

### RocksDB transaction lock timeout controlled internally

<small>Deprecated in: v3.12.6</small>

The `--rocksdb.transaction-lock-timeout` startup option has been deprecated.
It was supposed to let you configure the wait timeout in milliseconds for
locking a document in a transaction. However, the lock timeout is actually set
to differnet values internally, depending on what is a meaningful timeout for
a given case.

## Client tools

### arangodump
Expand Down