Project

General

Profile

Actions

Tasks #3118

closed

QA: radosgw upstart: test the radosgw upstart script respawn functionality

Added by Anonymous over 11 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Low
Assignee:
-
Target version:
-
% Done:

0%

Tags:
Reviewed:
Affected Versions:
Pull request ID:

Description

I have a vague bug report from Carl that radosgw, using the upstart script, is not restarting properly. Let's reproduce that (and add this to our manual QA, for now!)

1. Deploy radosgw using the upstart scripts. Find out what the PID of the process is. Kill it.
Upstart should restart it immediately; that is: Check that radosgw s running.

2. Ensure radosgw is running again. Using e.g. killall, kill radosgw more than 5 times in 30 seconds. Upstart should NOT restart it anymore, to prevent busy looping etc (radosgw.conf says "respawn limit 5 30", http://upstart.ubuntu.com/cookbook/#respawn ). Check that radosgw is NOT running.

3. After the respawn limit was hit, confirm that radosgw is down ("sudo initctl list|grep radosgw"), and run "sudo start radosgw-all". Check that radosgw is running.

If these all match expected, then either Carl's findings are unexplained, or we get to talk about what are the right settings for "respawn limit".

Actions

Also available in: Atom PDF