Bug 1569548
Summary: | Change the fluentd request timeout to be essentially infinite | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Jeff Cantrill <jcantril> |
Component: | Logging | Assignee: | ewolinet |
Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.7.1 | CC: | anli, aos-bugs, ewolinet, jcantril, nhosoi, pportant, rmeggins, tkatarki |
Target Milestone: | --- | ||
Target Release: | 3.7.z | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
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-18 03:54:45 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: | |||
Bug Depends On: | 1559404, 1569550 | ||
Bug Blocks: |
Comment 1
Jeff Cantrill
2018-04-19 13:23:12 UTC
The bug have been fixed in v3.7.46. 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 |