Actions
Bug #20339
closedrgw stops serving requests after receiving SIGHUP
Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
Yes
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Hi.
We're running Ceph kraken (v11.2.0) on CentOS 7 and have noticed that after receiving a SIGHUP, radosgw stops processing requests.
In the logs we're observing the following error messages:
2017-06-19 00:01:03.592113 7f832be9e700 1 rgw realm reloader: Frontends paused 2017-06-19 00:01:03.592339 7f8349eda700 0 ERROR: failed to clone shard, completion_mgr.get_next() returned ret=-125
Updated by Casey Bodley almost 7 years ago
SIGHUP will pause frontends while it reloads the realm/period configuration for multisite. Are you not seeing a corresponding 'Resuming frontends with new realm configuration.' message in the log?
Updated by Casey Bodley almost 7 years ago
- Status changed from New to Need More Info
Updated by Yehuda Sadeh almost 7 years ago
I vaguely remember seeing something similar, maybe this:
http://tracker.ceph.com/issues/19834
Updated by Yuri Gorshkov almost 7 years ago
Hi Casey,
No, I don't see the 'Resuming...' message when the frontend crashes. For now we've just resorted to restarting rgws when they hang.
Updated by Casey Bodley almost 7 years ago
- Related to Bug #20686: rgw hangs in RGWRealmReloader::reload on SIGHUP added
Updated by Casey Bodley over 2 years ago
- Status changed from Need More Info to Closed
Actions