Project

General

Profile

Subtask #6888

Feature #4929: Erasure encoded placement group

EC/Tiering: Disallow omap writes on pools which are backed by EC pools

Added by Samuel Just almost 6 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11/22/2013
Due date:
% Done:

100%

Estimated time:
0.00 h
Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

EC will not allow omap at all in the first cut. Support will require a kind of "omap_append" operation which only creates keys, but cannot overwrite or remove them. Otherwise, we'd have to include rollback information in the pg log.


Related issues

Blocked by Ceph - Subtask #6895: omap needs to be disablable on a per-pool basis, this needs to be required to cache an EC pool Rejected 11/25/2013

History

#1 Updated by Neil Levine almost 6 years ago

  • Project changed from devops to Ceph
  • Target version deleted (v0.74)

#2 Updated by Loic Dachary over 5 years ago

  • Status changed from New to In Progress
  • Assignee set to Loic Dachary

#3 Updated by Loic Dachary over 5 years ago

  • Parent task set to #4929

#4 Updated by Loic Dachary over 5 years ago

  • Status changed from In Progress to Need More Info
  • Assignee deleted (Loic Dachary)

Is it possible to implement this before implementing ErasureCodePG ?

#5 Updated by Greg Farnum over 5 years ago

It should be able to; this will be stuff in the caching and tiering code to look at the properties on the backing pool and disable stuff it the backing pool will disallow it.

#6 Updated by Loic Dachary over 5 years ago

  • Status changed from Need More Info to Resolved
  • translation missing: en.field_remaining_hours set to 0.0

In firefly

#7 Updated by Loic Dachary over 5 years ago

  • % Done changed from 0 to 100
  • Estimated time set to 0.00 h

Also available in: Atom PDF