Project

General

Profile

Actions
Copy link

Feature #41564

closed

Issue health status warning if num_shards_repaired exceeds some threshold

Added by David Zafman over 4 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
David Zafman
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
nautilus,octopus
Reviewed:
Affected Versions:
Component(RADOS):
Pull request ID:
35514

Description

Now that num_shards_repaired has been added, we can assist in noticing disk, controller, software or other issues by warning if this number exceeds some value.

Should we have a way to reset it?

Related issues 3 (0 open — 3 closed)

Related to RADOS - Bug #46405: osd/osd-rep-recov-eio.sh: TEST_rados_repair_warning: return 1ResolvedDavid Zafman

Actions
Copied to RADOS - Backport #46095: octopus: Issue health status warning if num_shards_repaired exceeds some thresholdResolvedNathan CutlerActions
Copied to RADOS - Backport #46096: nautilus: Issue health status warning if num_shards_repaired exceeds some thresholdResolvedDavid ZafmanActions
Actions
Copy link
 #1

Updated by David Zafman almost 4 years ago

  • Status changed from New to In Progress
  • Pull request ID set to 35514
Actions
Copy link
 #2

Updated by Neha Ojha almost 4 years ago

  • Backport set to nautilus,octopus
Actions
Copy link
 #3

Updated by David Zafman almost 4 years ago

  • Status changed from In Progress to Pending Backport
Actions
Copy link
 #4

Updated by Patrick Donnelly almost 4 years ago

  • Copied to Backport #46095: octopus: Issue health status warning if num_shards_repaired exceeds some threshold added
Actions
Copy link
 #5

Updated by Patrick Donnelly almost 4 years ago

  • Copied to Backport #46096: nautilus: Issue health status warning if num_shards_repaired exceeds some threshold added
Actions
Copy link
 #6

Updated by Neha Ojha almost 4 years ago

  • Related to Bug #46405: osd/osd-rep-recov-eio.sh: TEST_rados_repair_warning: return 1 added
Actions
Copy link
 #7

Updated by Nathan Cutler over 3 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions
Copy link

Also available in: Atom PDF