Project

General

Profile

Bug #1351

rados bench should report errors

Added by Greg Farnum almost 8 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
qa
Target version:
Start date:
08/02/2011
Due date:
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:

Description

Right now if you get eg a perm error on write, rados bench just keeps looping waiting for the write to complete. That's clearly wrong, and wherever the problem is it should be propagated back to the user and result in program termination.

History

#1 Updated by Sage Weil almost 8 years ago

  • Target version changed from v0.34 to v0.35
  • translation missing: en.field_position set to 1

#2 Updated by Sage Weil almost 8 years ago

  • translation missing: en.field_position deleted (11)
  • translation missing: en.field_position set to 31

#3 Updated by Sage Weil almost 8 years ago

  • Target version changed from v0.35 to v0.36
  • translation missing: en.field_position deleted (29)
  • translation missing: en.field_position set to 1

#4 Updated by Sage Weil over 7 years ago

  • translation missing: en.field_story_points set to 1
  • translation missing: en.field_position deleted (43)
  • translation missing: en.field_position set to 37

#5 Updated by Sage Weil over 7 years ago

  • Target version deleted (v0.36)
  • translation missing: en.field_position deleted (43)
  • translation missing: en.field_position set to 8

#6 Updated by Josh Durgin over 7 years ago

  • Priority changed from Normal to High

This is probably what caused #1734.

#7 Updated by Sage Weil over 7 years ago

  • Target version set to v0.39
  • translation missing: en.field_position deleted (41)
  • translation missing: en.field_position set to 6

#8 Updated by Sage Weil over 7 years ago

  • Assignee set to Greg Farnum

#9 Updated by Greg Farnum over 7 years ago

Quick skim analysis:
If there's an error, the OSD returns it as an ACK.
The objecter only sends back data on the replies you requested. So if you asked for a commit and get an ack, it drops it on the floor. But the OSD is done, so...
Hang!

Should be a simple matter of getting the objecter to return any error return code to all requested contexts. (Although I'm not sure rados bench actually checks them, so there's that too.)

#10 Updated by Greg Farnum over 7 years ago

  • Status changed from New to Resolved

Also available in: Atom PDF