ability to only duplicate unicorn master, while retaining old master #29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem statement: Currently,
unicorn:restartalways kills the old master in a definite( but configurable) time interval, vizunicorn_restart_sleep_time. But If the new master has not booted up and ready to accept requests before this time, it can lead to service downtime.Exposing the
unicorn:duplicateallows clients to only duplicate the unicorn, creating a new master with updated code. The onus to make sure old master is killed later, falls on the client with this. A cool client level solution for the same is found here - https://yhbt.net/unicorn/examples/unicorn.conf.rb