For an object that's subject to both erasure coding and shredding:
•Each time a full copy of the data for the object is reduced to a chunk, the full copy must be shredded
•Each time a chunk for the object is restored to a full copy of the object data, the chunk must be shredded
As a result, shredding objects that are subject to erasure coding can put a significant load on all the systems in the replication topology across which the objects are erasure coded.
To minimize the load that the combination of erasure coding and shredding can put on an HCP system, take one of these actions:
•At the system level, do not enable erasure coding as an option for implementing replicaton.
•If you enable erasure coding as the replication method for all cloud-optimized namespaces, tell tenant administrators not to set shredding as the default for deleted objects in cloud-optimized namespaces that are selected for replication.
•If you allow tenant administrators to select erasure coding for their namespaces, tell the adiministrators not to do both of these for any given namespace:
oSet shredding as the default for deleted objects in
oAllow erasure coding
© 2015, 2020 Hitachi Vantara LLC. All rights reserved.