Actions
Subtask #6888
closedFeature #4929: Erasure encoded placement group
EC/Tiering: Disallow omap writes on pools which are backed by EC pools
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:
100%
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.
Updated by Neil Levine over 10 years ago
- Project changed from devops to Ceph
- Target version deleted (
v0.74)
Updated by Loïc Dachary over 10 years ago
- Status changed from New to In Progress
- Assignee set to Loïc Dachary
Updated by Loïc Dachary over 10 years ago
- Status changed from In Progress to Need More Info
- Assignee deleted (
Loïc Dachary)
Is it possible to implement this before implementing ErasureCodePG ?
Updated by Greg Farnum over 10 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.
Updated by Loïc Dachary about 10 years ago
- Status changed from Need More Info to Resolved
- Translation missing: en.field_remaining_hours set to 0.0
In firefly
Updated by Loïc Dachary about 10 years ago
- % Done changed from 0 to 100
- Estimated time set to 0:00 h
Actions