Pro Plan Elastic search max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

ciocca-devPRO

10 months ago

Pro Plan Elastic search max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

Solved

4 Replies

10 months ago

Hey there,

Unfortunately at this time, this setting wouldn't be something that can be changed.


Status changed to Awaiting User Response railway[bot] 10 months ago


ciocca-devPRO

10 months ago

big problem


Status changed to Awaiting Railway Response railway[bot] 10 months ago


10 months ago

I've created a ticket to triage this issue and will update you when I have more information, but for now this wouldnt be possible to change, please look for tweaks you could make to the software itself so it wouldn't need a high vm.max_map_count value.


Status changed to Awaiting User Response railway[bot] 10 months ago


Status changed to Solved brody 10 months ago


Status changed to Open brody 10 months ago


10 months ago

Hello,

This topic came up again and i've since worked on a solution.

Template: https://railway.app/template/elasticsearch

The needed fix: https://github.com/railwayapp-templates/elasticsearch/blob/main/elasticsearch.yml#L7

Let me know if this template works for you!


Status changed to Solved brody 10 months ago


Pro Plan Elastic search max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144] - Railway Help Station