Hi,
After reading the AWS blog for using open distro with Kubernetes I’ve raised a number of issues and PRs on the community GitHub project many months ago, but nobody seems to be picking them up.
For example, using the supplied master configuration could result in data loss .
1 Like
Hi @jimmyjones - Thanks for flagging! Have bumped up review requests from the devs working on k8s support for Open Distro.
opendistro-for-elasticsearch:master ← jimmyjones2:min_masters
opened 07:11PM - 17 Jun 19 UTC
NUMBER_OF_MASTERS set the config variable minimum_master_nodes so I have renamed… it to better explain what it does. That should be set to the minimum number of master nodes for quorum to prevent spit brain, ie 2 with this configuration of 3 masters.
The current configuration of three means that if the Kubernetes node running the master suddenly disappears there will be an elasticsearch outage until Kubernetes creates a new master elsewhere as neither of the remaining two master eligible nodes will assume the role of master. Once this patch is applied there will be no outage as one of the remaining two master eligible nodes will assume the master role.
See https://www.elastic.co/guide/en/elasticsearch/reference/6.8/discovery-settings.html#minimum_master_nodes
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
opendistro-for-elasticsearch:master ← jimmyjones2:delete_data_svc
opened 07:58PM - 18 Jun 19 UTC
I can't see a usecase for going directly to the data nodes and the pires configu… rations didn't have this. All access to the cluster should be through the elasticsearch service to client nodes.
In addition this service was publishing ports 9200, 9300 and 9600 yet the data node statefulset was only publishing 9300.