Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Hi, I'M Trying To Deploy Clearml On Gke On Google Cloud Via Helm Using App Version 1.0.2 And Chart Version 2.0.2+1. I'M Seeing The Following

Hi, I'm trying to deploy clearML on GKE on google cloud via helm using app version 1.0.2 and chart version 2.0.2+1. I'm seeing the following Cannot allocate memory warnings and errors in my clearml-elastic-master-0 pod.
| elasticsearch OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. │ elasticsearch {"type": "server", "timestamp": "2021-05-28T13:59:54,162Z", "level": "WARN", "component": "o.e.b.JNANatives", "cluster.name": "clearml-elastic", "node.name": "clearml-elas │ tic-master-0", "message": "Unable to lock JVM Memory: error=12, reason=Cannot allocate memory" } │ elasticsearch {"type": "server", "timestamp": "2021-05-28T13:59:54,165Z", "level": "WARN", "component": "o.e.b.JNANatives", "cluster.name": "clearml-elastic", "node.name": "clearml-elas │ tic-master-0", "message": "This can result in part of the JVM being swapped out." } │ elasticsearch {"type": "server", "timestamp": "2021-05-28T13:59:54,166Z", "level": "WARN", "component": "o.e.b.JNANatives", "cluster.name": "clearml-elastic", "node.name": "clearml-elas │ tic-master-0", "message": "Increase RLIMIT_MEMLOCK, soft limit: 16777216, hard limit: 16777216" } │ elasticsearch {"type": "server", "timestamp": "2021-05-28T13:59:54,166Z", "level": "WARN", "component": "o.e.b.JNANatives", "cluster.name": "clearml-elastic", "node.name": "clearml-elas │ tic-master-0", "message": "These can be adjusted by modifying /etc/security/limits.conf, for example: \n\t# allow user 'elasticsearch' mlockall\n\telasticsearch soft memlock unlimited\n │ \telasticsearch hard memlock unlimited" } │ elasticsearch {"type": "server", "timestamp": "2021-05-28T13:59:54,167Z", "level": "WARN", "component": "o.e.b.JNANatives", "cluster.name": "clearml-elastic", "node.name": "clearml-elas │ tic-master-0", "message": "If you are logged in interactively, you will have to re-login for the new limits to take effect." } ... later in logs | elasticsearch ERROR: [1] bootstrap checks failed │ elasticsearch [1]: memory locking requested for elasticsearch process but memory is not lockedI imagine I could make the changes specified in the warning to /etc/security/limits.conf and make my own slightly modified docker image, but I was wondering if anyone has seen this before and if there's something obvious I'm missing. I'm using all defaults in the values.yaml file currently.

Posted 3 years ago
Votes Newest

Answers 3

Hmm, I'm seeing the same environment variable already set on the clearml-elastic-master-0 pod. I'll have to look into this further, but any other thoughts are appreciated.

Posted 3 years ago

Hi StaleHippopotamus38

I imagine I could make the changes specified in the warning to 


Yep seems like elastic memory issue, but I think the helm chart takes care of it,
You can see a reference in the docker compose:

Posted 3 years ago

I'm sorry wrong line reference:
I'm assuming the error is due to ulimit missing:
try adding 16777216 to both soft/hard ulimit

Posted 3 years ago