Description of problem: This is just a clone of the 4.x bugzilla Bug 1741663 - Fluentd single pod logging performance regression in 4.x but for the 3.11 Version-Release number of selected component (if applicable): 3.11 it seems that in the mentioned bugzilla, the idea was to expose rotate_wait parameter to fluentd.
https://github.com/openshift/openshift-ansible/pull/11999 adds ansible support as well
https://github.com/openshift/origin-aggregated-logging/pull/1779 has merged
Verified. Once we enable openshift_logging_fluentd_refresh_interval=6&openshift_logging_fluentd_rotate_wait=6. The Containers logs are can be controlled by them. sh-4.2# env |grep CONTAINER_LOGS_ CONTAINER_LOGS_REFRESH_INTERVAL=6 CONTAINER_LOGS_ROTATE_WAIT=6 sh-4.2# grep -r refresh_interval dynamic/input-docker-default-docker.conf: refresh_interval 6 sh-4.2# grep -r rotate_wait dynamic/input-docker-default-docker.conf: rotate_wait 6
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:4050
Hi, I am re-opening this bug because the customer is still hitting it, even if less frequently. Customer environment: pods running for more than 3 weeks of an application that writes 2G of logs in less than 2days. Docker options are --log-opt max-size=2G --log-opt max-file=2
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days