Project

General

Profile

Feature #1410

teuthology: mark osds down in thrasher

Added by Sage Weil almost 8 years ago. Updated almost 8 years ago.

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

0%

Spent time:
Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

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...)

History

#1 Updated by Sage Weil almost 8 years ago

  • translation missing: en.field_position set to 4

#2 Updated by Sage Weil almost 8 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

#3 Updated by Greg Farnum almost 8 years ago

  • Status changed from New to In Progress
  • Assignee set to Greg Farnum

#4 Updated by Greg Farnum almost 8 years ago

  • Status changed from In Progress to Resolved

#5 Updated by Greg Farnum almost 8 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.

Also available in: Atom PDF