Bug 1707557 - JOURNAL_READ_FROM_HEAD defaults to true
Summary: JOURNAL_READ_FROM_HEAD defaults to true
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.9.z
Assignee: Rich Megginson
QA Contact: Anping Li
URL:
Whiteboard:
Depends On: 1707176 1707524 1707556
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-07 19:08 UTC by Rich Megginson
Modified: 2019-07-05 06:59 UTC (History)
6 users (show)

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.
Clone Of: 1707556
Environment:
Last Closed: 2019-07-05 06:58:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift origin-aggregated-logging pull 1635 0 None closed [release-3.9] Bug 1707557 - JOURNAL_READ_FROM_HEAD defaults to true 2020-11-27 02:21:30 UTC
Red Hat Product Errata RHBA-2019:1642 0 None None None 2019-07-05 06:59:13 UTC

Comment 4 Qiaoling Tang 2019-06-28 06:19:26 UTC
Verified in logging-fluentd-v3.9.85-1

Comment 6 errata-xmlrpc 2019-07-05 06:58:57 UTC
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:1642


Note You need to log in before you can comment on or make changes to this bug.