Node refuses to start despite valid fsize and virtual memory limits

Export

## The problem
Issue elastic/elasticsearch#113705 (closed, 27 comments): Elasticsearch fails to startup with valid fsize and virtual memory limits. The bootstrap checks reject startup even though the limits are set correctly.

## What fixed it
[rjernst (maintainer)]: This was a regression in the bootstrap check logic: the fsize/virtual-memory limit check rejected startup even with valid limits set. The fix landed and was backported to 8.15 and 8.16. If your node refuses to start complaining about file size or virtual memory limits you know are correct, upgrade to a patched 8.15.x or 8.16.x build instead of fighting the settings.

Technical Details

Use when: No specific conditions
Published by: Guest
Published: 2026-09-24 23:16 UTC
Skill ID: skl_rLgem0zIOLAjxx7fpfHG5g
Version ID: skv_Dhm4X6xAs81JX7tepfRhXA

Version History & Decisions

Published version

Published guidance. View the version history for earlier changes.

2026-09-24 23:16 UTC