)]}'
{"elasticsearch/values.yaml":[{"author":{"_account_id":30777,"name":"Steven Fitzpatrick","email":"steven@fitzpatrick.wtf","username":"sf280x"},"change_message_id":"4f73487534ddf13ce2d235ea3f10fdbd5af3d3a2","unresolved":true,"context_lines":[{"line_number":558,"context_line":"    -Dfile.encoding\u003dUTF-8"},{"line_number":559,"context_line":"    -Djna.nosys\u003dtrue"},{"line_number":560,"context_line":"    -XX:-OmitStackTraceInFastThrow"},{"line_number":561,"context_line":"    -Dio.netty.noUnsafe\u003dtrue"},{"line_number":562,"context_line":"    -Dio.netty.noKeySetOptimization\u003dtrue"},{"line_number":563,"context_line":"    -Dio.netty.recycler.maxCapacityPerThread\u003d0"},{"line_number":564,"context_line":"    -Dlog4j.shutdownHookEnabled\u003dfalse"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"01f8dcd6_381c7d8c","side":"PARENT","line":561,"updated":"2021-03-10 23:03:22.000000000","message":"I\u0027m not an expert on JVM tuning, so there may be no reason to specify these options anymore. But would you please elaborate on why you remove these completely instead of specifying JVM version, like the others?","commit_id":"cda359ef1fadaa8771c88d8aef01effa28ffe50b"},{"author":{"_account_id":32408,"name":"Sofiia Tavrovska","email":"tavrovskayasofya87@gmail.com","username":"stavrovska"},"change_message_id":"be372c3a4562682cb9bd7106fe98d0cb83b2b9c0","unresolved":true,"context_lines":[{"line_number":558,"context_line":"    -Dfile.encoding\u003dUTF-8"},{"line_number":559,"context_line":"    -Djna.nosys\u003dtrue"},{"line_number":560,"context_line":"    -XX:-OmitStackTraceInFastThrow"},{"line_number":561,"context_line":"    -Dio.netty.noUnsafe\u003dtrue"},{"line_number":562,"context_line":"    -Dio.netty.noKeySetOptimization\u003dtrue"},{"line_number":563,"context_line":"    -Dio.netty.recycler.maxCapacityPerThread\u003d0"},{"line_number":564,"context_line":"    -Dlog4j.shutdownHookEnabled\u003dfalse"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"d83fcda5_ec7b9f8f","side":"PARENT","line":561,"in_reply_to":"01f8dcd6_381c7d8c","updated":"2021-03-11 17:22:37.000000000","message":"Elasticsearch image version 7.9.0 added mandatory bootstrap setting\u0027s check before start. These bootstrap checks inspect a variety of Elasticsearch and system settings and compare them to values that are safe for the operation of Elasticsearch. If Elasticsearch is in production mode, any bootstrap checks that fail will cause Elasticsearch to refuse to start. \n(https://www.elastic.co/guide/en/elasticsearch/reference/current/bootstrap-checks.html)\nBecause Elasticsearch image 7.9.0 has JVM version 14.0 it fails with previous jvm-options loaded from helm chart. To start elasticsearch-master pods without failures it needs to use default JVM options or custom options, but be ready that these settings may not pass bootstrap check.\n\nJVM options, that I provided, are default options from Elasticsearch JVM config, and as Elasticsearch documentation says: \"Elasticsearch includes default JVM options that work well for most production environments. If needed, you can override these default options using jvm.options files\". Unfortunately, I don\u0027t have possibility to validate all possible versions and options compatibility for JVM 14 and Elasticsearch \u003e\u003d 7.7.0.","commit_id":"cda359ef1fadaa8771c88d8aef01effa28ffe50b"}]}