Actions
Bug #19430
closedobjecter: full_try behavior not consistent with osd
Status:
Resolved
Priority:
Urgent
Assignee:
-
Category:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
jewel,kraken
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
on the objecter, we have
bool respects_full() const { return (target.flags & (CEPH_OSD_FLAG_WRITE | CEPH_OSD_FLAG_RWORDERED)) && !(target.flags & (CEPH_OSD_FLAG_FULL_TRY | CEPH_OSD_FLAG_FULL_FORCE)); }
which means that we do resend after full only if neither full_try nor full_force are set.
but on the osd,
if (write_ordered && !( m->get_source().is_mds() || m->has_flag(CEPH_OSD_FLAG_FULL_FORCE)) && info.history.last_epoch_marked_full > m->get_map_epoch()) { dout(10) << __func__ << " discarding op sent before full " << m << " " << *m << dendl; return; }
Updated by Sage Weil about 7 years ago
- Related to Bug #19133: osd ops (sent and?) arrive at osd out of order added
Updated by Sage Weil about 7 years ago
- Backport set to jewel
Updated by Sage Weil about 7 years ago
- Status changed from New to Fix Under Review
Updated by Sage Weil about 7 years ago
- Has duplicate Bug #19540: .../rados/test.sh: line 9: 29593 Terminated (times out) added
Updated by Sage Weil about 7 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport changed from jewel to jewel,kraken
Updated by Nathan Cutler about 7 years ago
- Copied to Backport #19559: jewel: objecter: full_try behavior not consistent with osd added
Updated by Nathan Cutler about 7 years ago
- Copied to Backport #19560: kraken: objecter: full_try behavior not consistent with osd added
Updated by Nathan Cutler over 6 years ago
- Status changed from Pending Backport to Resolved
Actions