Merge compatible node pools

You can create a node class compatibility to merge multiple compatible node pools. Larger node pools, up to 20 nodes, enable OneFS to protect data more efficiently, therefore providing more storage space for new data.

About this task

For example, if you have six S200 nodes in one node pool and three S210 nodes in a second node pool, you can create a compatibility to merge the two node pools into one nine-node pool.
Note Image

Newer node types typically have better performance specifications than older node types, so merging them with older node types can reduce overall performance. Also, when two node pools are merged, OneFS restripes the data, which can take considerable time, depending on the size of your data set.

Procedure

  1. Click File System > Storage Pools > SmartPools.
    The SmartPools tab displays two lists: Tiers & Node Pools and Compatibilities.
  2. Click Create a compatibility.
    The Create a Compatibility dialog box displays a drop-down list of compatibility types.
  3. From the Compatibility Type list, select Node Class.
    Two additional drop-down lists are added, First Node Class and Second Node Class.
  4. In the First Node Class list, accept the current selection, or make a new selection.
  5. In the Second Node Class list, accept the current selection, or make a new selection.
  6. Click Create Compatibility.
    A Confirm Create Compatibility dialog box appears, with one or more check boxes that you must select before proceeding. The check boxes describe the results of the operation.
  7. Select all check boxes, and then click Confirm.

Results

The node class compatibility is created, and is also described in the Compatibilities list. For example, a message such as "The S200 Node Class is now considered compatible with the S210 Node Class" is displayed. The result of the new compatibility appears in the Tiers & Node Pools list. If compatibility creation succeeds, but the node pools are not merged, you probably need to create an SSD compatibility between the two node pools. If compatibility creation fails with an error message, L3 cache is disabled on one or both of the node pools.