Project

General

Profile

Documentation #3166

doc: Explain OSD up/down, in/out: what does it mean, where does it come from

Added by Anonymous over 11 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

Something like: up/down is observed by peers, spread via gossip, reaches monitors that make a decision to declare an osd down. in/out is a human decision, except there's that one flag that says if an osd is down for X time, then make it go out.

History

#1 Updated by Ross Turk over 11 years ago

  • translation missing: en.field_position set to 1
  • translation missing: en.field_position changed from 1 to 1395

#2 Updated by Ross Turk over 11 years ago

  • translation missing: en.field_position deleted (1395)
  • translation missing: en.field_position set to 30

#3 Updated by Patrick Donnelly over 5 years ago

  • Project changed from Ceph to RADOS

#4 Updated by Zac Dover about 4 years ago

  • Status changed from New to Closed

This bug has been judged too old to fix. This is because either it is either 1) raised against a version of Ceph prior to Luminous, or 2) just really old, and untouched for so long that it is unlikely nowadays to represent a live documentation concern.

If you think that the closing of this bug is an error, raise another bug of a similar kind. If you think that the matter requires urgent attention, please let Zac Dover know at .

Also available in: Atom PDF