Skip to content

docs: document ha.appendElementLimit setting #413

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.

Sign up for GitHub

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

Merged
robfrank merged 1 commit into from
Jun 30, 2026
Merged

docs: document ha.appendElementLimit setting #413

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
1 change: 1 addition & 0 deletions src/main/asciidoc/reference/settings.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,6 +114,7 @@ The following plugins are available for ArcadeDB Server:
|Name|Description|Type|Default Value
|`backup.enabled`|State of backup lock. Disable for increased performance of massive insertions.|Boolean|True
|`ha.appendBufferSize`|AppendEntries batch byte limit for replication (e.g. '4MB'). _Since v26.4.1_|String|4MB
|`ha.appendElementLimit`|Maximum number of Raft log entries per AppendEntries batch. Bounds the per-batch in-memory footprint on the follower during catch-up resync, where many batches may queue before the state machine can apply them. Lowering this value reduces peak heap pressure on followers catching up from a far-behind state. The byte limit (`ha.appendBufferSize`) remains the dominant per-batch heap bound; this element count is the secondary cap that governs when entries are small enough that many fit under the byte limit. Must be a positive integer (>= 1). _Since v26.7.1_|Integer|64
|`ha.clientElectionRetryCount`|Number of retries performed by RemoteDatabase after receiving HTTP 503 NeedRetryException during an election. _Since v26.4.1_|Integer|3
|`ha.clientElectionRetryDelayMs`|Delay in ms between RemoteDatabase election retries. _Since v26.4.1_|Long|2000
|`ha.bootstrapFromLocalDatabase`|When true (default), at first cluster formation peers exchange `(fingerprint, lastTxId)` per database; the highest-`lastTxId` peer is elected as bootstrap source via leadership transfer. Matching peers bootstrap locally with zero bytes transferred; mismatched peers reinstall the leader-shipped full snapshot. _Since v26.5.1_|Boolean|true
Expand Down
Loading