E-ES: ElasticSearch Memory Lock Setting Fails

(Doc ID 2335438.1)

Last updated on DECEMBER 06, 2017

Applies to:

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

Goal

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".

http://<esad31.xxx.org:35246/_nodes/process?pretty.>

{
  "cluster_name" : "ESDEV",
  "nodes" : {
  "3qMvFDaIR4iROR5tuxpFog" : {
  "name" : "esad31",
  "transport_address" : "<esad31.xxx.org/10.200.8.90:9300>",
  "host" : "10.200.8.90",
  "ip" : "10.200.8.90",
  "version" : "2.3.2",
  "build" : "b9e4a6a",
  "http_address" : "<esad31.xxx.org/10.200.8.90:35246>",
  "process" : {
  "refresh_interval_in_millis" : 1000,
  "id" : 917,
  "mlockall" : false
  }
  }
  }
}

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

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms