Try to increase vm.max_map_count=262144 if not running on a container (else get blocked)

Bug #1824392 reported by Alvaro Uria
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
elasticsearch (Juju Charms Collection)
New
Undecided
Unassigned

Bug Description

ES service won't start because:
"""
[1] bootstrap checks failed
[1]: max virtual memory areas vm.max_map_count [65530] is too low,
increase to at least [262144]
"""

The charm should try to modify the value (and add a /etc/sysctl.d/99-elasticsearch.conf) if it's not a container. Otherwise, charm should get blocked and advice the user to change such value.

Revision history for this message
Peter Sabaini (peter-sabaini) wrote :

The PR https://github.com/elastic/elasticsearch/pull/21899 introduces a
knob to prevent ES from demanding vm.max_map_count increases, could also try to set this when running in a container with low vm.max_map_count

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.