Bug #1351
closed
rados bench should report errors
Added by Greg Farnum over 12 years ago.
Updated over 12 years ago.
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.
- Target version changed from v0.34 to v0.35
- Translation missing: en.field_position set to 1
- Translation missing: en.field_position deleted (
11)
- Translation missing: en.field_position set to 31
- Target version changed from v0.35 to v0.36
- Translation missing: en.field_position deleted (
29)
- Translation missing: en.field_position set to 1
- Translation missing: en.field_story_points set to 1
- Translation missing: en.field_position deleted (
43)
- Translation missing: en.field_position set to 37
- Target version deleted (
v0.36)
- Translation missing: en.field_position deleted (
43)
- Translation missing: en.field_position set to 8
- Priority changed from Normal to High
This is probably what caused #1734.
- Target version set to v0.39
- Translation missing: en.field_position deleted (
41)
- Translation missing: en.field_position set to 6
- Assignee set to Greg Farnum
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.)
- Status changed from New to Resolved
Also available in: Atom
PDF