<p dir="auto">See <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="40075849" data-permission-text="Title is private" data-url="https://github.com/elastic/elasticsearch/issues/7241" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/7241/hovercard?comment_id=52343350&amp;comment_type=issue_comment" href="https://github.com/elastic/elasticsearch/pull/7241#issuecomment-52343350">#7241 (comment)</a></p>
<p dir="auto">After <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="163898513" data-permission-text="Title is private" data-url="https://github.com/elastic/elasticsearch/issues/19272" data-hovercard-type="pull_request" data-hovercard-url="/elastic/elasticsearch/pull/19272/hovercard" href="https://github.com/elastic/elasticsearch/pull/19272">#19272</a>, Elasticsearch instances will now die after hitting a fatal error (e.g., out of memory error). The breaking changes documentation associated with this change includes the note:</p>
<blockquote>
<p dir="auto">Operators should consider configuring their Elasticsearch services so that they respawn automatically in the case of such a fatal crash.</p>
</blockquote>
<p dir="auto">The question put forth here is: should the Elasticsearch packages attempt to configure this? The challenge here is that this is not straightforward on System V init-based systems (<code class="notranslate">/etc/inittab</code>) but it is straightforward on systemd-based systems.</p>
<p dir="auto">Marking this as <a href="https://github.com/elastic/elasticsearch/labels/discuss">discuss</a>.</p>