Bug 1573957

Summary: [DOCS] Elasticsearch node count size cannot be scaled down (resized) using the logging playbook
Product: OpenShift Container Platform Reporter: Nicolas Nosenzo <nnosenzo>
Component: DocumentationAssignee: Brandi Munilla <bmcelvee>
Status: CLOSED CURRENTRELEASE QA Contact: Anping Li <anli>
Severity: low Docs Contact: Vikram Goyal <vigoyal>
Priority: unspecified    
Version: 3.7.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-06-04 16:19:45 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 Nicolas Nosenzo 2018-05-02 15:02:34 UTC 
Document URL: 
https://docs.openshift.com/container-platform/3.5/install_config/aggregate_logging.html#aggregated-elasticsearch

https://docs.openshift.com/container-platform/3.6/install_config/aggregate_logging.html#aggregated-elasticsearch

https://docs.openshift.com/container-platform/3.7/install_config/aggregate_logging.html#aggregated-elasticsearch

https://docs.openshift.com/container-platform/3.9/install_config/aggregate_logging.html#aggregated-elasticsearch


Section Number and Name: 

Changing the Scale of Elasticsearch

Describe the issue: 

Currently, documentation states the following:

"""
The simplest way to change the scale of Elasticsearch is to modify the inventory host file a re-run the logging playbook as desribed previously. Assuming you have supplied persistent storage for the deployment, this should not be disruptive.
"""
Although, this is only possible when openshift_logging_es_cluster_size is bigger than the current ES cluster size. When openshift_logging_es_cluster_size is smaller, then openshift-logging playboo will fail. 
https://github.com/openshift/openshift-ansible/blob/master/roles/openshift_logging_elasticsearch/tasks/main.yaml#L10-L12

Suggestions for improvement: 

Add a note stating the following:

"""
Resize an Elasticsearch cluster using the logging playbook is only possible when the new openshift_logging_es_cluster_size value is higher than the current number of ES nodes (scale up) in the cluster.
"""

Additional information:
Comment 2 Brandi Munilla 2018-05-21 16:14:41 UTC 
Hi Anping, 

I opened the following PR with the note and minor text edits to the previous paragraph. 

https://github.com/openshift/openshift-docs/pull/9456

PTAL, thanks!
Comment 3 Anping Li 2018-05-22 01:55:12 UTC 
@Brandi, LGTM
Comment 4 openshift-github-bot 2018-05-31 21:30:09 UTC 
Commits pushed to master at https://github.com/openshift/openshift-docs

https://github.com/openshift/openshift-docs/commit/d71367cd6761b17900041e40c017342ae1699aa4
Bug 1573957 Added note clarifying ES sizing

https://github.com/openshift/openshift-docs/commit/67fbdbbd52ca6cb7d546062e42cf123ee6e020d9
Merge pull request #9456 from bmcelvee/BZ1573957

Bug 1573957 Added note clarifying ES sizing
Comment 5 Brandi Munilla 2018-06-04 16:19:45 UTC 
Link to documentation on the customer portal: https://access.redhat.com/documentation/en-us/openshift_container_platform/3.9/html-single/installation_and_configuration/#aggregated-elasticsearch