Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1644686

Summary: Increased file i/o using experimental logging-fluentd based on 1.2.x
Product: OpenShift Container Platform Reporter: Mike Fiedler <mifiedle>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED ERRATA QA Contact: Mike Fiedler <mifiedle>
Severity: low Docs Contact:
Priority: medium    
Version: 4.1.0CC: aos-bugs, ematysek, rmeggins
Target Milestone: ---   
Target Release: 4.2.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: aos-scalability-40
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-16 06:27:40 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:
Attachments:
Description Flags
Decreased IOPS after new fluentd version used. none

Description Mike Fiedler 2018-10-31 12:09:33 UTC 
Description of problem:

This is a tracker for https://github.com/fluent/fluentd/issues/2153.   A place to discuss any possible actions on the OpenShift side (changes to tagging, event streams, etc) or provide additional results beyond what is already in the issue

Version-Release number of selected component (if applicable): OCP 4.0
Comment 3 Mike Fiedler 2019-08-22 11:18:37 UTC 
Claimed fixed upstream in fluentd 1.7.   See closing comment in https://github.com/fluent/fluentd/issues/2153
Comment 6 Mike Fiedler 2019-09-20 03:20:55 UTC 
Verified on fluentd v4.2.0-201909162219.

Logging 3000 1Kb messages/second across 20 namespaces on a fluentd - no message loss and IOPS averaged 65 read and 39 write over the course of the run  vs the ~1000 write IOPS seen in the original issue.
Comment 7 Mike Fiedler 2019-09-20 04:04:57 UTC 
Created attachment 1617016 [details]
Decreased IOPS after new fluentd version used.
Comment 9 errata-xmlrpc 2019-10-16 06:27:40 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:2922