Bug 1575903

Summary: Default value for openshift_logging_elasticsearch_memory_limit is too small
Product: OpenShift Container Platform Reporter: Junqi Zhao <juzhao>
Component: LoggingAssignee: Jeff Cantrill <jcantril>
Status: CLOSED ERRATA QA Contact: Junqi Zhao <juzhao>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.9.0CC: aos-bugs, pportant, rmeggins, wsun
Target Milestone: ---Keywords: Regression
Target Release: 3.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
undefined
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-07-30 19:14:54 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 Junqi Zhao 2018-05-08 08:54:57 UTC
Description of problem:
Default value for openshift_logging_elasticsearch_memory_limit is too small, it is only 1Gi, original value was 8Gi, it's better to change back

Version-Release number of selected component (if applicable):
# rpm -qa | grep openshift-ansible
openshift-ansible-roles-3.9.27-1.git.0.52e35b5.el7.noarch
openshift-ansible-docs-3.9.27-1.git.0.52e35b5.el7.noarch
openshift-ansible-playbooks-3.9.27-1.git.0.52e35b5.el7.noarch
openshift-ansible-3.9.27-1.git.0.52e35b5.el7.noarch

#  grep -r "openshift_logging_elasticsearch_memory_limit"
roles/openshift_logging/tasks/install_logging.yaml:    openshift_logging_elasticsearch_memory_limit: "{{ openshift_logging_es_ops_memory_limit }}"
roles/openshift_logging/tasks/install_logging.yaml:    openshift_logging_elasticsearch_memory_limit: "{{ openshift_logging_es_ops_memory_limit }}"
roles/openshift_logging/tasks/set_defaults_from_current.yml:          __openshift_logging_elasticsearch_memory_limit: elasticsearch.resources.limits.memory
roles/openshift_logging/tasks/set_defaults_from_current.yml:      openshift_logging_elasticsearch_memory_limit: openshift_logging_elasticsearch_memory_limit | __openshift_logging_elasticsearch_memory_limit
roles/openshift_logging_elasticsearch/defaults/main.yml:openshift_logging_elasticsearch_memory_limit: "{{ openshift_logging_es_memory_limit | default('1Gi') }}"
roles/openshift_logging_elasticsearch/tasks/main.yaml:    es_memory_limit: "{{ openshift_logging_elasticsearch_memory_limit }}"
roles/openshift_logging_elasticsearch/templates/2.x/es.j2:              value: "{{openshift_logging_elasticsearch_memory_limit}}"
roles/openshift_logging_elasticsearch/templates/5.x/es.j2:              value: "{{openshift_logging_elasticsearch_memory_limit}}"

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
Default value for openshift_logging_elasticsearch_memory_limit is 1Gi

Expected results:
Default value for openshift_logging_elasticsearch_memory_limit should be 8Gi

Additional info:

Comment 3 openshift-github-bot 2018-06-21 23:31:03 UTC
Commits pushed to master at https://github.com/openshift/openshift-ansible

https://github.com/openshift/openshift-ansible/commit/04fb9b4ccab2337f22365fe38cfeda7daf4ec624
bug 1575903. Default ES memory to 8G

https://github.com/openshift/openshift-ansible/commit/3ef81eee7c59fb3aeb9b1b1b78ae0d45ef444236
Merge pull request #8761 from jcantrill/1575903_es_mem

bug 1575903. Default ES memory to 16G

Comment 4 Jeff Cantrill 2018-06-22 18:11:05 UTC
3.10 PR https://github.com/openshift/openshift-ansible/pull/8931

Comment 6 Junqi Zhao 2018-07-09 01:03:20 UTC
Default value for openshift_logging_elasticsearch_memory_limit, openshift_logging_es_memory_limit and  openshift_logging_es_ops_memory_limit is 16Gi now

# rpm -qa | grep openshift-ansible
openshift-ansible-docs-3.10.14-1.git.273.a64b86b.el7.noarch
openshift-ansible-playbooks-3.10.14-1.git.273.a64b86b.el7.noarch
openshift-ansible-3.10.14-1.git.273.a64b86b.el7.noarch
openshift-ansible-roles-3.10.14-1.git.273.a64b86b.el7.noarch

Comment 8 errata-xmlrpc 2018-07-30 19:14:54 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/RHBA-2018:1816