Bug #14081
closedThe radosgw-agent cannot unlock, and error code is 404
0%
Description
When the "rgw_num_rados_handles" is set as 16, the radosgw-agent cannot unlock, the error code is 404. the log is as following:
......
2015-12-13 21:52:33,373 26594 [radosgw_agent.lock][WARNING] failed to unlock shard 115 in zone zone-a: Http error code 404 content Not Found
......
2015-12-13 21:53:00,732 26594 [radosgw_agent.lock][ERROR ] locking shard 116 in zone zone-a failed: Http error code 423 content
......
I can find the locker with the "rados lock info" command, and break the lock with "rados lock break" command.
I find the reason finally, the reason is that the lock request from radosgw-agent is processed by a rados client and the unlock request from radosgw-agent is processed by anther rados client. When the "rgw_num_rados_handles" is set as 1, the warning message did not appeared.
The above case also appeared when more than one radosgw instance are deployed.
Updated by Yehuda Sadeh over 8 years ago
- Assignee set to Orit Wasserman
- Priority changed from Normal to High
Updated by Matt Benjamin over 7 years ago
- Status changed from New to In Progress
- Priority changed from High to Normal
Updated by Casey Bodley over 7 years ago
- Related to Bug #17907: multisite: unlock failure added
Updated by Casey Bodley about 4 years ago
- Status changed from In Progress to Closed