Bug 1569054
Summary: | fluentd's NUM_OUTPUTS only takes secure_forward count into account | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | François Cami <fcami> | |
Component: | Logging | Assignee: | Noriko Hosoi <nhosoi> | |
Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | unspecified | CC: | aos-bugs, jcantril, rmeggins | |
Target Milestone: | --- | |||
Target Release: | 3.9.z | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | logging-fluentd-docker-v3.9.22-2 | Doc Type: | Bug Fix | |
Doc Text: |
Cause:
We currently compute the number of fluentd outputs in the startup script run.sh. When the forward plugin is configured, it was not correctly counted.
Consequence:
We miss a number of output when the forward plugin is configured. The number of output is used for calculating the file buffer size and the size gets larger than expected.
Fix:
The logic of the calculation was fixed to include the forward plugin case.
Result:
The correct output number then the correct file buffer size is now derived when the forward plugin is configured.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1569544 1569554 (view as bug list) | Environment: | ||
Last Closed: | 2019-01-30 15:10:24 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1569544, 1569554 |
Description
François Cami
2018-04-18 14:39:32 UTC
PR: https://github.com/openshift/origin-aggregated-logging/pull/1021 Commit: https://github.com/openshift/origin-aggregated-logging/pull/1021/commits/1ee717be49cf31b5d9755e4addd6bdb10921f46f The fix is in v3.9.64-4. 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:0098 |