Bug 1962122 - Elasticsearch request and cpu limits should be the same value
Summary: Elasticsearch request and cpu limits should be the same value
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 4.7
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.7.z
Assignee: landerso
QA Contact: Xiaoli Tian
Petr Kovar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-19 10:44 UTC by Oscar Casal Sanchez
Modified: 2021-12-01 17:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-01 14:51:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift openshift-docs issues 32638#issuecomment-945195490 0 None closed [enterprise-4.7] Issue in file logging/config/cluster-logging-log-store.adoc 2021-10-18 11:01:35 UTC
Red Hat Issue Tracker RHDEVDOCS-3095 0 Unprioritized Open Bug 1962122 - Elasticsearch request and cpu limits should be the same value 2021-06-18 13:50:52 UTC
Red Hat Issue Tracker RHDEVDOCS-3428 0 None None None 2021-11-10 22:08:51 UTC

Description Oscar Casal Sanchez 2021-05-19 10:44:35 UTC
[Document URL] 
https://docs.openshift.com/container-platform/4.7/logging/config/cluster-logging-log-store.html#cluster-logging-logstore-limits_cluster-logging-store

[Section Number and Name] 
Configuring CPU and memory requests for the log store

[Describe the issue] 
The example is having different values for limits.memory and request.memory and the values should be the same.

This is the example:

~~~
      elasticsearch:
        resources: 
          limits:
            memory: 16Gi
          requests:
            cpu: "1"
            memory: "64Gi"
~~~

And it should be like this:
~~~
      elasticsearch:
        resources: 
          limits:
            memory: 16Gi
          requests:
            cpu: "1"
            memory: 16Gi
~~~

or

~~~
      elasticsearch:
        resources: 
          limits:
            memory: 64Gi
          requests:
            cpu: "1"
            memory: 64Gi
~~~

At the same time, not only the value, the request.memory has the value between " " and the limits.memory not. Then, not consistency in the example. It's ok without " "

Comment 1 Oscar Casal Sanchez 2021-05-19 10:52:33 UTC
Hello,

At the same time, this is happening in the doc for OCP 4.5 (not for 4.6) here:

  https://docs.openshift.com/container-platform/4.5/logging/config/cluster-logging-log-store.html#cluster-logging-logstore-limits_cluster-logging-store

Comment 2 Rolfe Dlugy-Hegwer 2021-05-20 12:20:03 UTC
I found various discrepancies in each version.

1. Use git diff master..enterprise-4.8 modules/cluster-logging-logstore-limits.adoc
to compare master with the various release branches.
2. Migrate all valid changes and additions to master.
3. Manually cherry-pick master to each release branch.
4. Work with QE to ensure that a release branch does not receive invalid changes.

Comment 3 Oscar Casal Sanchez 2021-10-18 07:04:36 UTC
Hello,

Any news about this change proposed?

Thank you in advance,
Oscar

Comment 4 Rolfe Dlugy-Hegwer 2021-10-18 10:22:17 UTC
Hi Oscar,

For status, please see the Red Hat Issue Tracker in the Links section, above.

Rolfe

Comment 5 landerso 2021-11-10 22:10:28 UTC
Hi Oscar, a PR with the suggested changes has been submitted, along with a subtask for replacing instances of 8Gi values with 16Gi. Links to the issue for tracker for each have been added.


Note You need to log in before you can comment on or make changes to this bug.