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.

Elasticsearch stable Helm charts max file descriptors

See original GitHub issue

Stable Helm Elasticsearch charts https://github.com/helm/charts/tree/master/stable/elasticsearch fail on Elasticsearch nodes startup:

[2018-12-18T22:11:25,113][INFO ][o.e.b.BootstrapChecks    ] [es-elasticsearch-master-0] bound or publishing to a non-loopback address, enforcing bootstrap checks
ERROR: [1] bootstrap checks failed
[1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]

microk8s.inspect output:

Inspecting services
  Service snap.microk8s.daemon-docker is running
  Service snap.microk8s.daemon-apiserver is running
  Service snap.microk8s.daemon-proxy is running
  Service snap.microk8s.daemon-kubelet is running
  Service snap.microk8s.daemon-scheduler is running
  Service snap.microk8s.daemon-controller-manager is running
  Service snap.microk8s.daemon-etcd is running
  Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system info
  Copy network configuration to the final report tarball
  Copy processes list to the final report tarball
  Copy snap list to the final report tarball
  Inspect kubernetes cluster

 WARNING:  IPtables FORWARD policy is DROP. Consider enabling traffic forwarding with: sudo iptables -P FORWARD ACCEPT
Building the report tarball
  Report tarball is at /var/snap/microk8s/340/inspection-report-20181218_231630.tar.gz

On host:

cat /etc/sysctl.conf
vm.max_map_count = 262144
fs.file-max = 1634038

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:14 (5 by maintainers)

Top GitHub Comments

7reactions

ktsakalozoscommented, Apr 1, 2019

Ok here is a workaround that seems to be working (for me at least).

Edit /var/snap/microk8s/current/args/containerd-env and add this line at the end:

ulimit -n 65536

Then restart MicroK8s with microk8s.stop and microk8s.start. Your containerd should now have the limit set to 65536. Let me know it this worked.

2reactions

ephillcommented, Mar 26, 2019

@ktsakalozos Any pointers for doing the same thing using microk8s 1.14? Since the move to containerd these settings which were working for us are now being ignored obviously. Having trouble finding an equivalent setting in containerd.

Top Results From Across the Web

Elasticsearch stable Helm charts max file descriptors #253

In VM case, I only set proper host OS settings inside the Minikube VM. Is there particular issue to propagate fs.file-max to Microk8s...

File Descriptors | Elasticsearch Guide [8.5] | Elastic

RPM and Debian packages already default the maximum number of file descriptors to 65535 and do not require further configuration. You can check...

elasticsearch 7.15.0 · elastic/elastic - Artifact Hub

This Helm chart is a lightweight way to configure and run our official Elasticsearch Docker image. Requirements; Installing. Install released version using ...

stable/elasticsearch - helm-charts - GitLab

Parameter Description Default appVersion Application Version (Elasticsearch) 6.8.2 image.repository Container image name docker.elastic.co/elasticsearch/elastic... image.tag Container image tag 6.8.2

Helm Uninstall

Synopsis. This command takes a release name and uninstalls the release. It removes all of the resources associated with the last release of...