Feature #1410
closedteuthology: mark osds down in thrasher
0%
Description
this exercises some additional code paths. shouldn't be too frequent by default.
the 'wrongly marked down' thing presents as an ERR in the cluster log, so it would be nice if we could mask that particular error as well? or not, hmm!
(maybe the frequency of all the thrasher events should be tunable in the yaml, actually? so you can adjust the probabilities for different tests? then i could use it, say, only mark osds down with low frequency, or later use it to hammer on just the in/out code, or whatever...)
Updated by Sage Weil over 12 years ago
- Translation missing: en.field_position set to 4
Updated by Sage Weil over 12 years ago
- Translation missing: en.field_story_points set to 3
- Translation missing: en.field_position deleted (
28) - Translation missing: en.field_position set to 27
Updated by Greg Farnum over 12 years ago
- Status changed from New to In Progress
- Assignee set to Greg Farnum
Updated by Greg Farnum over 12 years ago
- Status changed from In Progress to Resolved
Completed in fb33ef3c69f6e5237c85c18b691f03545d1fce05
Updated by Greg Farnum over 12 years ago
This makes most everything configurable: frequency of status changes, approximate frequency of wait_till_clean()s, chance of marking an OSD down instead of out, min and max cluster membership.
It does not try and mask any resulting errors.