Skip to main content
NetApp Stage KB

How to configure and validate memory configuration for OCI running on RHEL or CentOS?

Views:
Visibility:
Public
Votes:
0
Category:
cloud-insights
Specialty:
oci
Last Updated:

Applies to

  • OnCommand Insight (OCI) 7.3.x
  • Red Hat Enterprise Linux (RHEL) or CentOS

Description

  • This article describes how to identify and manually set memory allocation for OCI components.
  • Component memory allocation may require adjustment in the following scenarios:
    • The amount of system memory (RAM) on the server hosting the application has changed since the application was installed.
    • NetApp has made recommendation for a specific environment.
  • OCI determines component memory allocation at the time of install based on the table below.
    Scale 1 2 3 4 5 6 7
    Operating System Configured Memory ≥ 25,576 MB ≥ 32,768 MB ≥ 49,152 MB ≥ 65,536 MB ≥ 98,304 MB ≥ 131,072 MB ≥ 262,144 MB
    Elasticsearch 6144 8192 16384 24576 30720 30720 30720
    MySQL 6144 6144 8192 10240 12288 16384 24576
    SANscreen Server (Wildfly)  5120 8192 10240 12288 16384 24576 32768
    Acquisition 2048 3072 4096 6144 8192 10240 12288
  • If configuration is not met, system health shows error:
    System Size
      Memory Size Configuration
      Invalid Memory Configuration
    Please contact support. MySQL innodb_buffer_pool_size set to 8192 MB, expected 10240 MB or more. Elastic search minimum and maximum heap size set to 16384 MB and 16384 MB, expected minimum and maximum heap size of 24576 MB or more, but no more than 30720 MB. WildFly maximum heap size set to 10240 MB, expected 12288 MB or more.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.
077e8862-042b-4368-881f-5cbe316358c5