Bug 1616354 - logging-fluentd needs to periodically reconnect to logging-mux or elasticsearch to help balance sessions
Summary: logging-fluentd needs to periodically reconnect to logging-mux or elasticsear...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.9.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 3.9.z
Assignee: Rich Megginson
QA Contact: Anping Li
URL:
Whiteboard:
Depends On: 1489533 1616352
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-15 16:48 UTC by Rich Megginson
Modified: 2018-09-22 04:53 UTC (History)
8 users (show)

Fixed In Version: openshift3/logging-fluentd:v3.9.41-1
Doc Type: Enhancement
Doc Text:
Feature: Fluentd will now reconnect to Elasticsearch every 100 operations by default. Reason: If one Elasticsearch is started before the others in the cluster, the load balancer in the Elasticsearch service will connect to that one and that one only, and so will all of the Fluentd connecting to Elasticsearch. Result: By having Fluentd reconnect periodically, the load balancer will be able to spread the load evenly among all of the Elasticsearch in the cluster.
Clone Of: 1616352
Environment:
Last Closed: 2018-09-22 04:53:09 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github uken fluent-plugin-elasticsearch pull 459 0 None None None 2018-08-15 16:48:40 UTC
Red Hat Product Errata RHBA-2018:2658 0 None None None 2018-09-22 04:53:57 UTC

Comment 2 Anping Li 2018-09-13 06:20:32 UTC 
Verified with logging:v3.9.43. The fluent connection are spread in all ES nodes.
Comment 4 errata-xmlrpc 2018-09-22 04:53:09 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-2018:2658
Note You need to log in before you can comment on or make changes to this bug.