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

build/ops: upstart: limit respawn to 3 in 30 mins (instead of 5 in 30s) #5930

Merged
1 commit merged into from Sep 15, 2015

Conversation

Projects
None yet
2 participants
@liewegas
Copy link
Member

commented Sep 14, 2015

upstart: limit respawn to 3 in 30 mins (instead of 5 in 30s)
It may take tens of seconds to restart each time, so 5 in 30s does not stop
the crash on startup respawn loop in many cases.  In particular, we'd like
to catch the case where the internal heartbeats fail.

This should be enough for all but the most sluggish of OSDs and capture
many cases of failure shortly after startup.

Fixes: #11798
Signed-off-by: Sage Weil <sage@redhat.com>
(cherry picked from commit eaff6cb)

@liewegas liewegas added this to the hammer milestone Sep 14, 2015

@liewegas liewegas added the build/ops label Sep 14, 2015

@ghost ghost self-assigned this Sep 14, 2015

ghost pushed a commit that referenced this pull request Sep 15, 2015

Loic Dachary
Merge pull request #5930 from liewegas/wip-11798-hammer
upstart: limit respawn to 3 in 30 mins (instead of 5 in 30s)

Reviewed-by: Loic Dachary <ldachary@redhat.com>

@ghost ghost merged commit 2b11a4c into ceph:hammer Sep 15, 2015

@ghost ghost changed the title upstart: limit respawn to 3 in 30 mins (instead of 5 in 30s) build/ops: upstart: limit respawn to 3 in 30 mins (instead of 5 in 30s) Sep 21, 2015

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.