Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1569548 - Change the fluentd request timeout to be essentially infinite
Change the fluentd request timeout to be essentially infinite
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging (Show other bugs)
3.7.1
All Linux
high Severity high
: ---
: 3.7.z
Assigned To: ewolinet
Anping Li
:
Depends On: 1559404 1569550
Blocks:
  Show dependency tree / graph
 
Reported: 2018-04-19 09:22 EDT by Jeff Cantrill
Modified: 2018-05-17 23:55 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: Bump up the fluentd timeout to be max unsigned int Reason: Currently we default the indexing request timeout for fluentd to 600 seconds. That is about 10 minutes. In certain situations, this timeout is not long enough. If we make this essentially infinite, we'll avoid fluentd pods re-submitting requests unnecessarily. Result: The fluentd timeout is 2147483648 and will wait for a very long time before resubmitting a request to ES due to a timeout failure
Story Points: ---
Clone Of: 1559404
Environment:
Last Closed: 2018-05-17 23:54:45 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github openshift/origin-aggregated-logging/pull/1041 None None None 2018-04-19 09:23 EDT
Red Hat Product Errata RHBA-2018:1576 None None None 2018-05-17 23:55 EDT

  None (edit)
Comment 3 Anping Li 2018-05-09 06:42:21 EDT 
The bug have been fixed in  v3.7.46.
Comment 6 errata-xmlrpc 2018-05-17 23:54:45 EDT 
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-2018:1576
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.