The log_collector service is blocked when the Elasticsearch cluster is too slow
Bug #1617211 reported by
Simon Pasquier
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StackLight |
Fix Released
|
Medium
|
Simon Pasquier | ||
0.10 |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In some environments (especially using slow HDD drives), the Elasticsearch backends may fail to ingest logs fast enough. As a result the log_collector service running on the controller nodes are blocked.
Changed in lma-toolchain: | |
assignee: | LMA-Toolchain Fuel Plugins (mos-lma-toolchain) → Simon Pasquier (simon-pasquier) |
status: | Triaged → In Progress |
Changed in lma-toolchain: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/356344 /git.openstack. org/cgit/ openstack/ fuel-plugin- lma-collector/ commit/ ?id=83db24f5496 d777232083f04f9 97fd60b9ab8663
Committed: https:/
Submitter: Jenkins
Branch: master
commit 83db24f5496d777 232083f04f997fd 60b9ab8663
Author: Swann Croiset <email address hidden>
Date: Wed Aug 17 11:38:10 2016 +0200
Increase the Elasticsearch bulk size when required
In some environments (especially using slow HDD drives), the
Elasticsearch backends may fail to ingest logs fast enough. As a result
the log_collector service running on the controller nodes are blocked.
To alleviate this issue, this change increases the bulk size for nodes
that generate lots of logs:
- controllers which run OpenStack API services in addition to Pacemaker.
- all nodes when the environment's log level is set to debug.
In such cases, the flush_count parameter is increased to 100 (instead of
10 by default).
Change-Id: Ifdfbcb8ff0292f 695dee4deab4556 0f126bde242
Closes-Bug: #1617211