My Oracle Support Banner

E-ES: How to have changes made to the ES_HEAP_SIZE environment variable reported correctly in the Elasticsearch log file (ESCLUSTER.LOG) (Doc ID 2424436.1)

Last updated on SEPTEMBER 11, 2018

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.56 and later
Microsoft Windows x64 (64-bit)

Goal

When initially installing the Elasticsearch DPKs, the initial Java Heap Size was set to 12G. Due to subsequent growth in data volume, the Heap Size needed to be increased. This was done by adding the ES_HEAP_SIZE environment variable and setting its value to 16G (ES_HEAP_SIZE=16G). However, after restarting Elasticsearch the ESCLUSTER.LOG still retained and reported the initial Heap Size of 12G. Additional actions need to be taken to cause the ESCLUSTER.LOG file to reflect the new/updated Java Heap Size.
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.