Project

General

Profile

Fix #10350

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

Associated revisions

Revision 02cab93f (diff)
Added by Loic Dachary about 9 years ago

documentation: add troubleshooting erasure coded PGs section

Add a new section to the PG troubleshooting section that covers the most
common problems reported when an erasure coded pool fails to properly
map PGs to enough OSDs.

http://tracker.ceph.com/issues/10350 Fixes: #10350

Signed-off-by: Loic Dachary <>

History

#1 Updated by Loïc Dachary over 9 years ago

  • Status changed from 12 to Fix Under Review
  • % Done changed from 0 to 80

#2 Updated by Loïc Dachary almost 9 years ago

  • Status changed from Fix Under Review to Resolved

#3 Updated by Greg Farnum almost 7 years ago

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

Also available in: Atom PDF