Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1553257 - [REF]-Use multiple primary shards for the .operations indices by default matching the number of data nodes in the cluster
[REF]-Use multiple primary shards for the .operations indices by default matc...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging (Show other bugs)
3.9.0
All Linux
high Severity low
: ---
: 3.9.z
Assigned To: Jeff Cantrill
Anping Li
:
Depends On: 1552977
Blocks:
  Show dependency tree / graph
 
Reported: 2018-03-08 10:14 EST by Jeff Cantrill
Modified: 2018-08-09 18:14 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: Allow the number if indices and replicas to be configured using environment variables Reason: The logs collected for infra services consumes a large portion of the available disk space. Spreading the data across available nodes by modifying the replica and shard settings allow Elasticsearch to better support these large amounts of data Result: Improved performance in Elasticsearch when there are large amounts of data from infra services.
Story Points: ---
Clone Of: 1552977
Environment:
Last Closed: 2018-08-09 18:13:46 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Github openshift/origin-aggregated-logging/pull/1018 None None None 2018-03-15 08:30 EDT
Red Hat Product Errata RHBA-2018:2335 None None None 2018-08-09 18:14 EDT

  None (edit)
Description Jeff Cantrill 2018-03-08 10:14:59 EST 
+++ This bug was initially created as a clone of Bug #1552977 +++

Sharding the .operations indices (and .orphan indices) using a primary shard count that matches the number of nodes in the cluster will provide for an even distribution of disk usage and load across cluster members to help with high operational logging rates.  

This has little effect in low logging rate situations.

--- Additional comment from Peter Portante on 2018-03-07 20:07:30 EST ---

See the following gist for an example: https://gist.github.com/portante/f8cfecad1c6b69cdc1736ce464501d6f
Comment 1 Jeff Cantrill 2018-03-08 10:29:26 EST 
Master change: https://github.com/openshift/origin-aggregated-logging/pull/1007
Comment 5 Anping Li 2018-04-17 00:45:24 EDT 
Seems the fix is not in openshift-ansible:v3.9.22 and logging-elasticsearch/images/v3.9.22-1.
Comment 8 Qiaoling Tang 2018-04-20 01:37:17 EDT 
The fix isn't in openshift v3.9.24 and logging-elasticsearch/images/v3.9.25-1.
Comment 12 Anping Li 2018-07-31 06:35:13 EDT 
Fix in 3.9.40
Comment 14 errata-xmlrpc 2018-08-09 18:13:46 EDT 
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:2335
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.