Should the Elasticsearch packages configure respawn?

[jasontedor]

After #19272, 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:

Operators should consider configuring their Elasticsearch services so that they respawn automatically in the case of such a fatal crash.

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 (/etc/inittab) but it is straightforward on systemd-based systems.

Marking this as discuss.

[jasontedor]

We discussed this during Fix-it-Friday. We will configure respawn for systemd-based systems. We will investigate providing respawn for the System V init-based systems, but since most Linux systems are migrating to systemd, we will accept inconsistency if providing it for System V init-based systems is onerous. We will also need to investigate the possibilities on Windows, can @elastic/microsoft help here?

[Mpdreamz]

Windows allows service to recover from failures quite elaborately:

Options also available on the command line, I'll cross reference this issue on the windows installer repos so we can ship with this OOB and try to allign with the *nix packages.

[jasontedor]

@Mpdreamz Right, the question is whether or not it's possible to build the installer to configure this automatically on installation.

[Mpdreamz]

Thats what I meant with shipping with this feature out of the box, yes it should be possible to configure this automatically during installation.

[jasontedor]

Thats what I meant with shipping with this feature out of the box, yes it should be possible to configure this automatically during installation.

+1

[russcam]

+1 - can be configured with sc.exe
On 15 Jul 2016 8:06 p.m., "Jason Tedor" notifications@github.com wrote:

Thats what I meant with shipping with this feature out of the box, yes it
should be possible to configure this automatically during installation.

+1

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub
#19438 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMtZ_9L5O_Zh3Mm3BTJ7nwCg7vOCeUSks5qV1uigaJpZM4JM2aV
.

[jasontedor]

Duplicates #25425