Bug 1448860 - Elasticsearch recover_after_nodes parameter should be set to cluster quorum value
Summary: Elasticsearch recover_after_nodes parameter should be set to cluster quorum v...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.6.0
Hardware: All
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: Jeff Cantrill
QA Contact: Xia Zhao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-08 12:56 UTC by Peter Portante
Modified: 2017-08-16 19:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-08-10 05:23:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1716 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.6 RPM Release Advisory 2017-08-10 09:02:50 UTC

Description Peter Portante 2017-05-08 12:56:27 UTC 
We need to ensure that the recover_after_nodes parameter is set to the cluster's quorum value.
Comment 1 Jeff Cantrill 2017-05-08 13:11:29 UTC 
Fixed in: https://github.com/openshift/openshift-ansible/pull/4113
Comment 2 openshift-github-bot 2017-05-13 21:20:37 UTC 
Commit pushed to master at https://github.com/openshift/openshift-ansible

https://github.com/openshift/openshift-ansible/commit/2505424d99ebd32a05f6dd33d0bd7474ca6e441e
bug 1448860. Change recovery_after_nodes to match node_quorum
Comment 4 Xia Zhao 2017-06-06 08:26:10 UTC 
It's fixed, verified on openshift v3.6.94, the Elasticsearch recover_after_nodes parameter was equal to cluster quorum value:

# oc rsh logging-es-data-master-hqad8ai3-1-k81wn
NODE_QUORUM=1
RECOVER_AFTER_NODES=1

ansible playbook version tested with:
openshift-ansible-playbooks-3.6.95-1.git.0.dbd2cf1.el7.noarch
Comment 6 errata-xmlrpc 2017-08-10 05:23:08 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/RHEA-2017:1716
Note You need to log in before you can comment on or make changes to this bug.