Skip to content

Conversation

@rjernst
Copy link
Member

@rjernst rjernst commented Jul 2, 2025

In the unexpected case that Elasticsearch dies due to a segfault or
other similar native issue, a core dump is useful in diagnosing the
problem. Yet core dumps are written to the working directory, which is
read-only for most installations of Elasticsearch. This commit changes
the working directory to the logs dir which should always be writeable.

rjernst added 2 commits July 2, 2025 08:19
In the unexpected case that Elasticsearch dies due to a segfault or
other similar native issue, a core dump is useful in diagnosing the
problem. Yet core dumps are written to the working directory, which is
read-only for most installations of Elasticsearch. This commit changes
the working directory to the logs dir which should always be writeable.
With the change to using the logs dir as the working dir of the
Elasticsearch process we need to ensure the logs dir exists within the
CLI instead of later during startup.

relates elastic#124966
@rjernst rjernst added backport auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) labels Jul 2, 2025
@rjernst
Copy link
Member Author

rjernst commented Aug 20, 2025

@elasticmachine update branch

@elasticsearchmachine elasticsearchmachine merged commit 6876b8c into elastic:8.19 Aug 20, 2025
22 checks passed
@rjernst rjernst deleted the env/logs_working_dir_8.19 branch August 20, 2025 19:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport v8.19.3

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants