Bug 1569550 - Change the fluentd request timeout to be essentially infinite
Summary: Change the fluentd request timeout to be essentially infinite
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.6.1
Hardware: All
OS: Linux
Target Milestone: ---
: 3.6.z
Assignee: ewolinet
QA Contact: Anping Li
Depends On: 1559404
Blocks: 1569548
TreeView+ depends on / blocked
Reported: 2018-04-19 13:25 UTC by Jeff Cantrill
Modified: 2018-05-17 07:59 UTC (History)
8 users (show)

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
Clone Of: 1559404
Last Closed: 2018-05-17 07:58:35 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift origin-aggregated-logging pull 1040 0 None None None 2018-04-19 13:25:57 UTC
Red Hat Product Errata RHBA-2018:1579 0 None None None 2018-05-17 07:59:26 UTC

Comment 2 Anping Li 2018-05-08 08:15:58 UTC
The request_timeout is 2147483648 in logging-fluentd:v3.

Comment 5 errata-xmlrpc 2018-05-17 07:58:35 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.


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