My Oracle Support Banner

E-ES: ElasticSearch Memory Lock Setting Fails (Doc ID 2335438.1)

Last updated on AUGUST 11, 2022

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.55 and later
Information in this document applies to any platform.


Memory locking for ElasticSearch is activated but it is not working.  It is is set in the elasticsearch.yml, using the "bootstrap.mlockall: true".

When the following is checked to verify the setting, it shows ""mlockall" : false".


  "cluster_name" : "ESDEV",
  "nodes" : {
  "3qMvFDaIR4iROR5tuxpFog" : {
  "name" : "esad31",
  "transport_address" : "<>",
  "host" : "",
  "ip" : "",
  "version" : "2.3.2",
  "build" : "b9e4a6a",
  "http_address" : "<>",
  "process" : {
  "refresh_interval_in_millis" : 1000,
  "id" : 917,
  "mlockall" : false

PT 8.55.19; ElasticSearch DPK version: ELASTICSEARCH-DPK-LNX-2.3.2_04 


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

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