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

Make upstart script respawn consul on crash #108

Merged
merged 1 commit into from
Jan 29, 2015
Merged

Make upstart script respawn consul on crash #108

merged 1 commit into from
Jan 29, 2015

Conversation

tgwizard
Copy link
Contributor

This could be configurable (whether to respawn, and the count/interval/unlimited), but I think it could be a future PR.

Is there a reason to not respawn if consul crashes?

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling de2965f on tgwizard:upstart-respawn into 7ea99ed on johnbellone:master.

@lyrixx
Copy link
Contributor

lyrixx commented Jan 13, 2015

👍 for the features

@tgwizard
Copy link
Contributor Author

@johnbellone what do you think?

@johnbellone
Copy link
Contributor

I personally don't see anything wrong with this. Since its a change in behavior we should just bump the minor revision.

Any thoughts @reset ?

@johnbellone
Copy link
Contributor

@tgwizard Is there any logic in Consul that is destructive on a restart? Assuming it crashed we want to make sure that we're not wiping out data. Otherwise, it 👍 !

@tgwizard
Copy link
Contributor Author

@johnbellone there seems to be no issue for me. I can sudo kill -9 $PID, the consul process dies, and then restarts and rejoins the cluster. I have rejoin_after_leave set to true in my consul config though, which is (I think) what causes the rejoin to work. Or perhaps not, since no leave was triggered.

johnbellone added a commit that referenced this pull request Jan 29, 2015
Make upstart script respawn consul on crash
@johnbellone johnbellone merged commit 52f6669 into sous-chefs:master Jan 29, 2015
@tgwizard tgwizard deleted the upstart-respawn branch February 2, 2015 21:30
@lock
Copy link

lock bot commented Apr 25, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants