Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

esConfig.elasticsearch.yml values breaks cluster discovery

See original GitHub issue

Chart version: 7.11.2

Kubernetes version: 1.19.7

Kubernetes provider: Baremetal/VM kubespray on OVH

Helm Version: 3.5.3

helm get all output (helm doesn’t allow me bare get method) https://gist.github.com/vanch/ec383243ee92bb34956cc31c9bf4a74d#file-helm-get-release

Describe the bug: If you set any value in esConfig.elasticsearch.yml, 3rd node won’t connect to 1+2 cluster. If you leave esConfig by default, everything is ok.

Steps to reproduce:

Set any overriding value to esConfig.elasticsearch.yml, e.g.:

esConfig:
  elasticsearch.yml: |
    http.max_content_length: 100mb

Create new cluster
Check cluster status and pods statuses

Expected behavior: Cluster is ready with all nodes discovered

Provide logs and/or server output (if relevant): https://gist.github.com/vanch/ec383243ee92bb34956cc31c9bf4a74d#file-failing-node-log

Issue Analytics

State:
Created 3 years ago
Comments:5 (2 by maintainers)

Top GitHub Comments

1reaction

jmlrtcommented, Mar 17, 2021

Hi @vanch, Thanks for opening this issue. Unfortunately we currently don’t have time to investigate every tickets so please be patient.

0reactions

botelastic[bot]commented, Oct 21, 2021

This issue has been automatically closed because it has not had recent activity since being marked as stale.

Top Results From Across the Web

Configuring Elasticsearch | Elasticsearch Guide [8.5] | Elastic

This method lets Elasticsearch Service automatically reject unsafe settings that could break your cluster. If you run Elasticsearch on your own hardware, use ......

[elasticsearch] Cannot run a single node cluster #312 - GitHub

esConfig : elasticsearch.yml: | discovery: type: single-node seed_hosts: "" ... I tried just overriding it in the values.yaml but that breaks ...

Elasticsearch cluster 'master_not_discovered_exception'

changing discovery.zen.minimum_master_nodes worked for me. I have used old ES config which had a different minimum_master_nodes . corrected it.

Unknown setting [searchguard.enterprise_modules_enabled]

Elasticsearch version: 7.10.2 Server OS version: CentOS 7 Ki… ... or check the breaking changes documentation for removed settings.

Deploying Elasticsearch Within Kubernetes - Rancher

Learn to deploy Elasticsearch on a Kubernetes cluster using Rancer. ... es-config data: elasticsearch.yml: | cluster.name: my-elastic-cluster network.host: ...