Bug 1707524
| Summary: | JOURNAL_READ_FROM_HEAD defaults to true | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Rich Megginson <rmeggins> | |
| Component: | Logging | Assignee: | Rich Megginson <rmeggins> | |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | unspecified | CC: | anli, aos-bugs, jcantril, pweil, rmeggins | |
| Target Milestone: | --- | |||
| Target Release: | 3.11.z | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause: The environment variable JOURNAL_READ_FROM_HEAD is set to the empty string. This causes the default value of read_from_head for the journald input to be true. When Fluentd starts up for the first time on a node, it reads in the entire journal.
Consequence: It may take hours for system messages to show up in Elasticsearch and Kibana.
Fix: Fluentd will check if the value is set _and_ is not empty, otherwise, it will use a default of false.
Result: Fluentd will read from the tail of the journal when it starts up on a new node.
|
Story Points: | --- | |
| Clone Of: | 1707176 | |||
| : | 1707556 (view as bug list) | Environment: | ||
| Last Closed: | 2019-06-26 09:08:09 UTC | Type: | --- | |
| 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: | 1707176 | |||
| Bug Blocks: | 1707556, 1707557 | |||
|
Comment 1
Rich Megginson
2019-05-07 17:14:28 UTC
merged upstream https://github.com/openshift/origin-aggregated-logging/commit/83731df20ae40bdc8ca91e4c0518e496e34138ed Verified with logging-fluentd:v3.11.117 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:1605 |