Skip to content
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

pipeline:out_s3: added store_dir_limit_size documentation #971

Closed
wants to merge 0 commits into from

Conversation

Claych
Copy link
Contributor

@Claych Claych commented Nov 15, 2022

Signed-off-by: Clay Cheng [email protected]

@PettitWesley
Copy link
Contributor

@Claych missing signoff on the commit

@Claych Claych force-pushed the master branch 2 times, most recently from 65489f1 to d9ec3f0 Compare November 15, 2022 01:46
@lecaros lecaros added waiting-for-user Waiting for user/contributors feedback or requested changes conflict Waiting on conflict to be resolved by contributor labels Dec 23, 2022
@@ -28,6 +28,7 @@ See [here](https://github.com/fluent/fluent-bit-docs/tree/43c4fe134611da471e706b
| upload\_chunk\_size | The size of each 'part' for multipart uploads. Max: 50M | 5,242,880 bytes |
| upload\_timeout | Whenever this amount of time has elapsed, Fluent Bit will complete an upload and create a new file in S3. For example, set this value to 60m and you will get a new file every hour. | 10m |
| store\_dir | Directory to locally buffer data before sending. When multipart uploads are used, data will only be buffered until the `upload_chunk_size` is reached. | /tmp/fluent-bit/s3 |
| store\_dir\_limit\_size | The size of the limitation for disk usage in S3. Limit the amount of s3 buffers in the `store_dir` to limit disk usage. Note: Use `store_dir_limit_size` instead of `storage.total_limit_size` which can be used to other plugins, because S3 has its own bufffering system. | 0, which means unlimited |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

3 fffs in buffering

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conflict Waiting on conflict to be resolved by contributor waiting-for-user Waiting for user/contributors feedback or requested changes waiting-on-code-merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants