This section explains how to configure Adaptive Data Protection for your Qumulo cluster during node-add operations.
-
Qumulo Core 6.1.0.1 and 6.1.1 support Adaptive Data Protection by letting you reconfigure your cluster’s fault tolerance level and storage efficiency only when you add nodes to your cluster.
Depending on your cluster, Qumulo Core shows configuration options that offer better fault tolerance levels, better storage efficiency, or both benefits. To enable Adaptive Data Protection for your cluster, you must contact the Qumulo Care team.
-
In Qumulo Core 6.1.2 (and higher), you can change your cluster’s data protection configuration when you add or replace nodes by using the
qqCLI.
Your cluster’s usable capacity doesn’t increase until the data protection reconfiguration is complete. Because data protection reconfiguration is a long process (that can take days or weeks), we don’t recommend beginning this process when your cluster is nearly running out of usable capacity. In this scenario, contact the Qumulo Care team.
To Add a Node with Adaptive Data Protection to a Qumulo Cluster
A cluster’s data protection configuration includes the stripe configuration (for example, 10.8) and the node fault tolerance level.
Ensure that your configuration and node order are correct. Unless you add more nodes, it isn’t possible to revert this operation or reorder nodes after adding them to a cluster.
-
To select the new data protection configuration for your nodes, contact the Qumulo Care team.
-
Rack and wire your new nodes and then power them on.
-
To determine the UUIDs of the nodes to add to your cluster, run the
qq unconfigured_nodes_listcommand. -
Write down the UUIDs of the nodes that you want to add to the cluster, in the order that you want to add them.
-
To add your nodes to the cluster, run the
qq add_nodescommand and specify the node UUIDs (their ordering in the command determines their ordering in the cluster), the configuration type, and the node fault tolerance level.In the following example, we change the stripe configuration to 10.8 and the node fault tolerance level to 2 nodes.
qq add_nodes \ --node-uuids 12345a6b-7c89-0d12-3456-78fe9012f345 \ abcde1f2-g3hi-j4kl-mnop-qr56stuv7wxy \ --target-stripe-config 10 8 \ --target-max-node-failures 2The following is example output.
Current cluster: Usable capacity: 600 TB Node fault tolerance level: 1 node With the selected node-add operation and data protection reconfiguration: Usable capacity: 800 TB Node fault tolerance level: 2 nodes -
To confirm the configuration with the selected node-add and data protection configuration operations, enter
yes.
Monitoring the Data Protection Reconfiguration Process
To view the progress of the three stages of the data protection reconfiguration process, log in to the Qumulo Core Web UI and click Cluster.
-
Qumulo Core begins to move data to new nodes in the cluster and the Qumulo Core Web UI displays the message Rebalancing for data protection reconfiguration.
-
Qumulo Core reencodes all data on your cluster and the Qumulo Core Web UI displays the message Reconfiguring data protection.
Note
In certain scenarios, this stage might appear to pause while the system performs preparatory work on the cluster.When this stage is complete, your data is protected according to the cluster’s new configuration and the system begins to use the new drive and node fault tolerance levels.
-
Qumulo Core adds new capacity to your cluster and the Qumulo Core Web UI displays the message Rebalancing.
If you initiated the reconfiguration process as part of a node replacement step, the system migrates data from the existing nodes in the cluster.
Cluster Availability During the Reconfiguration Process
Your cluster remains available throughout the data protection reconfiguration process.
-
You can upgrade Qumulo Core.
-
Your cluster maintains the ability to recover from node and drive failure automatically.
During the reconfiguration process, drive and node fault tolerance levels remain at the minimums that the existing and new configurations specify. For example, if your existing cluster has 2-node and 2-drive fault tolerance, and you initiate reconfiguration where the new configuration has 1-node and 3-drive fault tolerance, your cluster has 1-node and 2-drive fault tolerance during the reconfiguration process.
- To avoid impact to front-end workloads, Qumulo Core slows down the reconfiguration process automatically.
- When Qumulo Core finds missing nodes or drives, it pauses the reconfiguration process. When you replace or bring the nodes or drives online, the reconfiguration process continues.
- It isn't possible to add or replace nodes during the reconfiguration process.