Hi all,
There is the run.sh script that’s required for docker images deployment and internally it just invokes the default ignite.sh script prior to starting a node. So far, so good, but we discovered that it doesn’t propagate system signals to the JVM due to its internal logic and also lacks some configuration parameters, like JVM options, therefore we have rewritten it in https://issues.apache.org/jira/browse/IGNITE-13453 and hope to include it in 2.9 release. As it turned out there was another reason for modifying the script – there was no way of disabling JMX using it, i.e. to set -nojmx=1, the flag supported by ignite.sh. With the new version, JMX is disabled by default and should be turned on explicitly setting the JVM options, like -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=49112, Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false As far as I can remember, there were some drawbacks with the default JMX setting and ignite.sh – It reduces security and could conflict with the control.sh, since it’s trying to open the same port. But it’s the subject for a separate discussion. So the question is – do we need to set those properties by default (enable JMX), most likely copying them from ignite.sh or it’s fine to have JMX disabled by default for k8s/docker deployment? -- Alex.
