Closed lukas-vlcek closed 4 years ago
Do we need to do this for ES6?
This setting was introduced in ES 2.4 but it is no longer used in ES 5.x and later. I believe it was ignoder by ES 5.x but I would rather remove it. First, it does not apply, second, I can imagine Elasticsearch can become very strict and complain about this invalid setting on startup in later versions.
@lukas-vlcek did you find the source? do you have a PR to resolve? what is the impact?
To me it seems it is part of the image.
$ oc rsh elasticsearch-cdm-mm11mrt6-1-fcfc79457-52bnk
Defaulting container name to elasticsearch.
Use 'oc describe pod/elasticsearch-cdm-mm11mrt6-1-fcfc79457-52bnk -n openshift-logging' to see all of the containers in this pod.
sh-4.2$ echo $ES_JAVA_OPTS
-Dmapper.allow_dots_in_name=true
----- ^^^^^^^^^^ -----
sh-4.2$
OK, I found it here: https://access.redhat.com/containers/?tab=tech-details#/registry.access.redhat.com/openshift4/ose-logging-elasticsearch5 See the Env part that contains
ES_JAVA_OPTS=-Dmapper.allow_dots_in_name=true
Now, I need to track it back to its source :-)
Closing ticket. The issue is actually not in the code of this repo, it is in different repo, see the BZ link above.
I removed this settings in #1188 but it does not seem to be enough. The following is ES node log in OCP 4.1 (see the
ES_JAVA_OPTS
variable):We need to find out where this is being added into
ES_JAVA_OPTS
and remove it.