deploying elasticsearch in LXD container fails

Bug #1842617 reported by Yoshi Kadokawa
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Elasticsearch Charm
Expired
Medium
Unassigned

Bug Description

When deploying elasticsearch in LXD container, it will fail with the following error in /var/log/elasticsearch/elasticsearch.log

[1] bootstrap checks failed
[1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

When elasticsearch package is installed, it will try to set the vm.max_map_count with the following sysctl file.

# cat /usr/lib/sysctl.d/elasticsearch.conf
vm.max_map_count=262144

However, since it is in LXD container, this can not be configured, unless this is configured from the host.

As an workaround, increasing vm.max_map_count value in the host will mitigate the issue.

Revision history for this message
Celia Wang (ziyiwang) wrote :

Did you try to follow this doc https://github.com/lxc/lxd/blob/master/doc/production-setup.md to configure a set of value before lxd is initiated?
As we cannot configure this value in a container and can only configure on the host, is it still a bug for the container?
What do you think?

Changed in charm-elasticsearch:
status: New → Incomplete
Changed in charm-elasticsearch:
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Elasticsearch Charm because there has been no activity for 60 days.]

Changed in charm-elasticsearch:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.