Skip to content

Commit ade22bd

Browse files
authored
the storage pause feature is an input property.
1 parent 1ad572b commit ade22bd

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

administration/buffering-and-storage.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -48,10 +48,6 @@ It's common to find cases that if we have multiple destinations for a Chunk, one
4848

4949
Starting from Fluent Bit v1.6, we introduced the new configuration property for output plugins called `storage.total_limit_size` which limits the number of Chunks that exists in the file system for a certain logical output destination. If one destinations reaches the `storage.total_limit_size` limit, the oldest Chunk from it queue for that logical output destination will be discarded.
5050

51-
**Puasing on Storage Limit**
52-
53-
Using the boolean service property `storage.max_chunks_pause` inputs will pause once their chunks match or exceed the number of storage chunks they can have in the up stage, `storage.max_chunks_up`.
54-
5551
## Configuration
5652

5753
The storage layer configuration takes place in three areas:
@@ -96,6 +92,7 @@ Optionally, any Input plugin can configure their storage preference, the followi
9692
| Key | Description | Default |
9793
| :--- | :--- | :--- |
9894
| storage.type | Specify the buffering mechanism to use. It can be _memory_ or _filesystem_. | memory |
95+
| storage.max_chunks_pause | Specify if file storage is to be paused when reaching the chunk limit. | off |
9996

10097
The following example configure a service that offers filesystem buffering capabilities and two Input plugins being the first based in filesystem and the second with memory only.
10198

0 commit comments

Comments
 (0)