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

ciocca-dev
PRO

a year 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

a year ago

Hey there,

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


Status changed to Awaiting User Response Railway 12 months ago


ciocca-dev
PRO

a year ago

big problem


Status changed to Awaiting Railway Response Railway 12 months ago


a year 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 12 months ago


Status changed to Solved brody 12 months ago


Status changed to Open brody 12 months ago


a year 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 12 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