You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
Closeselastic#3685
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.
The text was updated successfully, but these errors were encountered: