Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1448860

Summary: Elasticsearch recover_after_nodes parameter should be set to cluster quorum value
Product: OpenShift Container Platform Reporter: Peter Portante <pportant>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED ERRATA QA Contact: Xia Zhao <xiazhao>
Severity: high Docs Contact:
Priority: high    
Version: 3.6.0CC: aos-bugs, jcantril, smunilla, xiazhao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-10 05:23:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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