Project

General

Profile

Actions
Copy link

Fix #10350

closed

explain how to troubleshoot erasure code mapping failures

Added by Loïc Dachary over 9 years ago. Updated almost 7 years ago.

Status:
Resolved
Priority:
High
Assignee:
Loïc Dachary
Category:
-
Target version:
-
% Done:

80%

Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

It is common to have X osd and create an erasure coded pool that requires X osd. The CRUSH rule is likely to fail mapping using the default chose trie of 50. The documentation should explain how to remedy to this situation. The default erasure coded crush ruleset should have a set choose_tries set to 200 to resolve the most common case.

Actions
Copy link
 #1

Updated by Loïc Dachary over 9 years ago

  • Status changed from 12 to Fix Under Review
  • % Done changed from 0 to 80
Actions
Copy link
 #2

Updated by Loïc Dachary about 9 years ago

  • Status changed from Fix Under Review to Resolved
Actions
Copy link
 #3

Updated by Greg Farnum almost 7 years ago

  • Project changed from Ceph to RADOS
  • Category deleted (10)
Actions
Copy link

Also available in: Atom PDF