Loading...

XML

Word

Printable

Blocked:
False
Ready:
False
Docs QE Status:
NEW
QE Status:
NEW
Release Note Text:

Hide
Before this update, the `ClusterLogging` custom resource (CR) applied the value of the `totalLimitSize` field to the Fluentd `total_limit_size` field, even if the required buffer space was not available. With this update, the CR applies the lesser of the two `totalLimitSize` or 'default' values to the Fluentd `total_limit_size` field, resolving the issue.

Show
Before this update, the `ClusterLogging` custom resource (CR) applied the value of the `totalLimitSize` field to the Fluentd `total_limit_size` field, even if the required buffer space was not available. With this update, the CR applies the lesser of the two `totalLimitSize` or 'default' values to the Fluentd `total_limit_size` field, resolving the issue.

When the `total_limit_size` for fluentd is configured according to the documentation, it allows to set any value larger than available disk space.

How reproducible:
Steps to Reproduce:
1. Deploy cluster-logging
2. Set very total_limit_size for fluentd
~~~~

3. View logs
~~~~

Actual results:

Setting each total_size_limit for 3 buffers to 107374182400 bytes

Setting queued_chunks_limit_size for each buffer to 12800

Setting chunk_limit_size for each buffer to 8388608

Expected Results:

Setting each total_size_limit for 3 buffers to 6415029657 bytes

Setting queued_chunks_limit_size for each buffer to 764

Setting chunk_limit_size for each buffer to 8388608

Additional info:

links to