Red Hat Bugzilla – Bug 1269271
Object Map & Erasure Coding documentation
Last modified: 2016-07-10 18:43:35 EDT
Index of objects that actually exist.
Valuable against clones that don't have actual objects, but gets object from parent.
Reads and writes that do copy ups.
Improves performance, because map has data already.
Off by default.
Can't do omap on erasure coded pool
Admin sets default user for placement/region/zone
Should have a hierarchy set up for different pools.
Add to Architecture Guide
Added content for Object Map in the following commit:
Provided the doc link to concerned devels for review.
As per devel review, updated the content in the following commit:
The Object Map content is now reviewed and finalized.
Fixed for 1.3.1 Release.