Comment from Discord:
"Plan for EC profile that is one less than total number of storage nodes. And for effective optimization of usage, make sure to choose the option to apply new EC to all objects from day 1.
"This would have negligible impact on performance. 2+1 has 50% overhead. 4+1 has 25% overhead. 6+1 reduces overhead to 17%.
"You need to strike a balance between fault tolerance, % of overhead, and your budget.
"rebalance-data start --site SITE_NAME"
SG 11.7: Considerations for rebalancing erasure-coded data (netapp.com)
SG 11.7: Rebalance erasure-coded data after adding Storage Nodes (netapp.com)
SG 11.7: Example 6: Change an ILM policy (netapp.com)
Can you modify an Erasure Coding Scheme in StorageGRID? - NetApp Knowledge Base
Can Erasure Coding Scheme conversion be monitored in StorageGRID? - NetApp Knowledge Base
Comment from Discord:
"Going from 6+1 to 8+2 requires data to be reconstructed to whole first before applying 8+2. Reconstruction of data requires a partial restore process to be initiated, to a point that data is whole before breaking it down to 8+2. Which is why you are seeing POST as opposed to GET network activity going up soon as new rule was initiated. This is the network activity between the storage related to reconstruct of data and then distribute it per the new rule."
SG 11.6: Monitor information lifecycle management (netapp.com)
SG 11.6: Operations on objects (netapp.com)
SG 11.6: POST Object restore (netapp.com)
SG 11.7: What and when to monitor (netapp.com) (Information You Should Monitor Regularly)
Comments
Post a Comment