OpenJDK Platform Binary (jave.exe) for Enterprise Vault Indexing consumes high memory.

book

Article ID: 100060258

calendar_today

Updated On:

Description

Error Message

N/A

Cause

Typically, JDK does use a considerable amount of memory during searches and indexing. With EV 14.2 and higher, the EVIndexingElasticSearch process, the garbage collection process periodically runs and reduces the amount of memory being utilized.

Resolution

Modify the Elasticsearch JVM heap size to a suitable value. The default value is 8192 MB and can be adjusted. It cannot exceed  50% of available RAM with a max setting of 32 GB..

1. Launch the Vault Admin Console.

2. Go to the Properties on the EV server name. In the Advanced tab, set the drop-down to Indexing

3. Modify the Elasticsearch JVM heap size.

4. Restart the Enterprise Vault Indexing Service. 

NOTE: Reducing the amount of memory may affect indexing performance. If possible, increase the overall amount of RAM on the EV server to allow for the increased memory usage by java.exe

Issue/Introduction

High CPU Utilization is seen for OpenJDK Platform Binary (java.exe) process.