Actions
Subtask #2236
closedFeature #2226: osd: better filestore idempotency test
filestore failure injection (3)
% Done:
0%
Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:
Description
add a hook to operations that we want to potentially fail.
need to identify the caller so that the tester can potentially trigger every failure point
enable via compilation flag
Updated by Sage Weil about 12 years ago
- Subject changed from filestore failure injection to filestore failure injection (3)
- Description updated (diff)
Updated by Sage Weil about 12 years ago
- Status changed from New to Resolved
wip-filestore-failure
I don't think enumerating/identifying the callers is needed here. For the idempotency tester the density of weirdness will be very high.
If need be, we can make a second --filestore-kill-foo-at with a parallel set of injection points, but this is enough for now.
Actions