Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deb/RPM: Disable immediate restart on package upgrade #3685

Closed
spinscale opened this issue Sep 13, 2013 · 0 comments
Closed

Deb/RPM: Disable immediate restart on package upgrade #3685

spinscale opened this issue Sep 13, 2013 · 0 comments

Comments

@spinscale
Copy link
Contributor

In order to have the possibility for unattended upgrades and to make sure, that these automatic upgrades do not start rebalancing the shards of a cluster around, the restart of elasticsearch after a package upgrade is now disabled by default. This is also important when providing repositories.

You can reenable it by setting RESTART_ON_UPGRADE=true in /etc/default/elasticsearch for debian packages or /etc/sysconfig/elasticsearch for redhat packages.

Note: This is a breaking change, as the debian package used to restart the elasticsearch service on every update, which now needs to be done by hand.

@ghost ghost assigned spinscale Sep 13, 2013
spinscale added a commit that referenced this issue Sep 13, 2013
Both package types, RPM and deb now contain an option to not restart on upgrade.

This option can be configure in /etc/default/elasticsearch for dpkg based systems
and /etc/sysconfig/elasticsearch for rpm based systems.

By default the setting is as before, where a restart is executed on upgrade.

Closes #3685
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
Both package types, RPM and deb now contain an option to not restart on upgrade.

This option can be configure in /etc/default/elasticsearch for dpkg based systems
and /etc/sysconfig/elasticsearch for rpm based systems.

By default the setting is as before, where a restart is executed on upgrade.

Closes elastic#3685
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant