taigrr/nats.docs
1
0
Fork 0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00
Code Issues Projects Releases Wiki Activity

Update storelimits.md

Browse Source
This commit is contained in:
Alexander Bogdanov 2020-02-06 19:50:46 +01:00 committed by GitHub
parent c28d1ebfa0
commit 0c9faaa484
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
nats-streaming-server/configuring/storelimits.md
View File

@ -139,7 +139,7 @@ On startup, the server will apply the store limits, which means that this channe
We strongly recommend not raising the limit back to the higher limit if messages have been removed in the previous step because those removed messages may or may not become available again depending on the store implementation or if running in clustering mode or not.
## Clustering
When running --clustered, messages are kept in RAFT consensus log file (under --cluster_log_path) in addition to the configured store.
When running --clustered, messages are kept in a RAFT consensus log file (under --cluster_log_path) in addition to the configured store.
This directory will grow as more messages keep coming within the 2-4 minute intervals of RAFT Snapshotting.
After snapshotting - the RAFT log will not shrink, but the space for more messages will be allocated internally.
After snapshotting the RAFT log will not shrink, but the space for more messages will be allocated internally.
As a result - in addition to max_bytes multiplied by max_channels - disk space needs to be provisioned for RAFT Log, which can grow up to the size of payloads that channels could receive per minute * 4.