-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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] On upgrade, restart kibana service #82049
Conversation
This adds a new environment variable KBN_RESTART_ON_UPGRADE with a default value of true. In an upgrade scenario Kibana will automatically restart. Closes elastic#9863
Targeting 8.0 with a default restart behavior, 7.11 with support for the flag but no change. Needs docs changes and this is just the outline for testing ATM, review pending undraft |
defaults /
https://s3-us-west-1.amazonaws.com/kibana.budzenski.com/82049/0b1d1f0/kibana-8.0.0-SNAPSHOT-amd64.deb |
Pinging @elastic/kibana-operations (Team:Operations) |
I believe in the past we discussed removing any interaction with the service in our scripts. Have you had different thoughts? What does ES currently do? |
This is modeled off ES, the main difference is UPGRADE_ON_RESTART in ES vs KBN_UPGRADE_ON_RESTART here. We could make them both the same name now that I'm thinking about it, environment variables are isolated in individual services. This should remove interaction by default on the builds above (but with a restart) but we were referring to not stopping the service right? I'll get some builds together and linky here with it removed to see how it runs. I'm mainly concerned with the unknowns - server routes going stale, not sure if the the public files are cached in memory. |
@elasticmachine merge upstream |
I replaced KBN_RESTART_ON_UPGRADE with RESTART_ON_UPGRADE to avoid any confusion and to be consistent with elasticsearch. The variable is scoped to the service so it shouldn't have any conflicts. For not stopping the service - I did an install where the service isn't stopped and didn't run into any issues. There were minimal code changes however, and another reason I'm trending towards this is migrations won't run. Any thoughts? |
@elasticmachine merge upstream |
@elasticmachine merge upstream |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - manually tested upgrade from 7.9.3
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: |
Co-authored-by: Kibana Machine <[email protected]>
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
1 similar comment
Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync. |
#82971) * [deb/rpm] On upgrade, restart kibana service (#82049) Co-authored-by: Kibana Machine <[email protected]> * default restart behavior to off in 7.x Co-authored-by: Kibana Machine <[email protected]>
7.11: 558ca4b < 8.0 will have a default behavior of not restarting. |
This adds a new environment variable
RESTART_ON_UPGRADE
with a default value of true. In an upgrade scenario, Kibana will automatically restart.Closes #9863
Release note:
Starting in 8.0 deb and rpm packages will restart on upgrade by default. This can be toggled by setting the environment variable
RESTART_ON_UPGRADE
in/etc/default/kibana