[Enhancement] simplify JAVA_OPTS in `start_fe.sh` about starrocks HOT 5 OPEN

@kevincai Doesn't it make sense to remove JAVA_OPTS_FOR_JDK_9 and JAVA_OPTS_FOR_JDK_11 from the default base values.yaml file? They are misleading.

ah, you are talking about the values.yaml for the helm chart installation. Yes, both can be removed from the default values.yaml

@yandongxiao

from starrocks.

the complication is introduced by the compatibility consideration if the user is upgraded from an old jdk version and then upgrade to the new one.

Ideally, if the user only provides JAVA_OPTS, it will be used as the final one, and if no JAVA_OPTS provided, the default one will be used.

from starrocks.

There are currently three places where JAVA_OPTS can be configured, which is confusing and increases the risk of mistakes.
According to our research, even when it is Java 11 environment, we need to config JAVA_OPTS_FOR_JDK_9 cc @mingmxu

Can we refactor the Helm chart to consolidate JAVA_OPTS into a single location in the values.yaml file?

https://github.com/StarRocks/starrocks-kubernetes-operator/blob/main/helm-charts/charts/kube-starrocks/values.yaml#L374-L376

from starrocks.

no. you can just clean all of the JAVA_OPTS_FOR_JDK9/JAVA_OPTS_FOR_JDK_11 all over the places and just keep the JAVA_OPTS in one place, that will take effect.

from starrocks.

@kevincai Doesn't it make sense to remove JAVA_OPTS_FOR_JDK_9 and JAVA_OPTS_FOR_JDK_11 from the default base values.yaml file?
They are misleading.

from starrocks.