When configuring and using storage pools, follow these guidelines.
Guidelines for all storage pools
- StorageGRID includes a default storage pool called All Storage Nodes that uses the default site, All Sites, and the All Storage Nodes storage grade. Because this storage pool is automatically updated whenever you add new data center sites, review the guidelines for replicated and erasure-coded copies before using this storage pool or the default site, All Sites.
- Keep storage pool configurations as simple as possible. Do not create more storage pools than necessary.
- Create storage pools with as many nodes as possible. Each storage pool should contain two or more nodes. A storage pool with insufficient nodes can cause ILM backlogs if that node becomes unavailable.
- Avoid creating or using storage pools that overlap (contain one or more of the same nodes). If storage pools overlap, more than one copy of object data might be saved on the same node.
Guidelines for storage pools used for replicated copies
- If your StorageGRID system includes more than one data center site, considering creating a storage pool for each site instead of using the default storage pool, All Storage Nodes, or a storage pool that includes the default site, All Sites. You can then specify those storage pools in the rule's placement instructions to enable site-loss protection of replicated copies.
Guidelines for storage pools used for erasure-coded copies
- You cannot use Archive Nodes for erasure-coded data.
- The number of Storage Nodes and sites contained in the storage pool determine which erasure coding schemes are available. No erasure coding schemes are available for a storage pool that has two sites.
- If you plan to create erasure-coded copies, create a new storage pool and manually add each site you want to include. Do not use the default storage pool, All Storage Nodes, or a storage pool that includes the default site, All Sites. This is to ensure that the erasure coding scheme does not become invalid when new sites are added. For example, if you currently have one site and use the All Storage Nodes storage pool, your Erasure Coding profile will become invalid if you add a second site.
- If you have high throughput requirements, creating a storage pool that includes multiple sites is not recommended if the network latency between sites is greater than 100 ms. As latency increases, the rate at which StorageGRID can create, place, and retrieve object fragments decreases sharply due to the decrease in TCP network throughput. The decrease in throughput affects the maximum achievable rates of object ingest and retrieval (when Strict or Balanced are selected as the Ingest Behavior) or could lead to ILM queue backlogs (when Dual Commit is selected as the Ingest Behavior).
- If possible, a storage pool should include more than the minimum number of Storage Nodes required for the erasure coding scheme you select. For example, if you use a 6+3 erasure coding scheme, you must have at least nine Storage Nodes. However, having at least one additional Storage Node per site is recommended.
- Distribute Storage Nodes across sites as evenly as possible. For example, to support a 6+3 erasure coding scheme, configure a storage pool that includes at least three Storage Nodes at three sites.
Guidelines for storage pools used for archived copies
- You cannot create a storage pool that includes both Storage Nodes and Archive Nodes. Archived copies require a storage pool that only includes Archive Nodes.
- When using a storage pool that includes Archive Nodes, you should also maintain at least one replicated or erasure-coded copy on a storage pool that includes Storage Nodes.
- If the global Compliance setting is enabled and you are creating a compliant ILM rule, you cannot use a storage pool that includes Archive Nodes. See "Managing S3 buckets and objects for compliance."
- If an Archive Node's Target Type is Cloud Tiering - Simple Storage Service (S3), the Archive Node must be in its own storage pool. See "Configuring connection settings for the S3 API."