Bug 1924258
| Summary: | fluentd fails to deliver message with Server returned nothing (no headers, no data) | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Sergey Yedrikov <syedriko> | |
| Component: | Logging | Assignee: | Sergey Yedrikov <syedriko> | |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | high | |||
| Version: | 4.6 | CC: | akaris, andcosta, anli, aos-bugs, apaladug, ddelcian, dgautam, gkarager, hchatter, igreen, jcantril, jswensso, mmohan, nnosenzo, openshift-bugs-escalate, periklis, puraut, qitang, stwalter, syedriko | |
| Target Milestone: | --- | |||
| Target Release: | 4.6.z | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | logging-exploration | |||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Cause:
The default HTTP read and write timeouts in the Elasticsearch proxy were set to 5 seconds.
Consequence:
The Elasticsearch proxy times out connections between fluentd and Elasticsearch too soon in some bulk insertion situations.
Fix:
Increase the default HTTP read and write timeouts in the Elasticsearch proxy to 1 minute. Provide command-line options in Elasticsearch proxy that control HTTP timeouts in the field.
Result:
The Elasticsearch proxy no longer times out connections between fluentd and Elasticsearch prematurely.
Command-line parameters of Elasticsearch proxy allow to control HTTP timeouts in Elasticsearch proxy in the field.
|
Story Points: | --- | |
| Clone Of: | 1908707 | |||
| : | 1924329 (view as bug list) | Environment: | ||
| Last Closed: | 2021-02-22 13:46:16 UTC | Type: | --- | |
| 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: | 1908707 | |||
| Bug Blocks: | 1924329 | |||
|
Comment 2
Giriyamma
2021-02-13 12:14:49 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 (OpenShift Container Platform 4.6.18 extras update), 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-2021:0512 |