Project

General

Profile

Bug #11667

erasure-code: test adding a new OSD

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

Status:
Resolved
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

  • create an erasure coded pool with a few objects
  • add a new osd
  • wait until the cluster is healthy
  • retrieve the objects

Associated revisions

Revision 8df81e05 (diff)
Added by Loic Dachary over 8 years ago

tests: verify erasure code read / write after remapping

Implement the following scenario:

  • create an erasure coded pool and write an object
  • mark two osd used to store the object out
  • wait until the PG is clean
  • read the object and compare it with the original
  • mark the two osd back in
  • wait until the PG is clean
  • read the object and compare it with the original

The scenario is run with the jerasure plugin only because the code path
involved does not vary depending on the erasure code plugin.

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

Signed-off-by: Loic Dachary <>

History

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

  • Status changed from 12 to Fix Under Review

#2 Updated by Sage Weil over 8 years ago

  • Status changed from Fix Under Review to Resolved

Also available in: Atom PDF