IN THIS ARTICLE
Outlines the details of running a multi-node cluster configuration of QF2 in AWS
- Account limits large enough for 20TB of EBS ST1 and 2TB of EBS GP2
- Permission to launch EC2 instances
- Single node m4.16xl EC2 instance
- No other instance types support clustered configurations at this time
EBS volume with one of the following configurations
- Five 100GB GP2 volumes
- Ten 500GB ST1 volumes
Four or more nodes running QF2 in AWS version 2.7.1 or higher
- The free trial AMI cannot run as a multi-node cluster
NOTE: Modifying the type or size of the EBS volumes in the QF2 AMI will render the software not functional. Please use the AMI volume layout provided in the original image.
Command line (qq CLI) tools installed via API & Tools in the Web UI
Running a clustered configuration of QF2 in AWS across 4 or more Qumulo nodes improves performance and increases capacity by providing a minimum of 20TB of raw storage. Larger systems with higher node numbers will have increased storage efficiency dependent on the initial number of nodes used to form the cluster. Before creating your QF2 in AWS cluster, consider the amount of storage and number of nodes that you need.
- SSH onto one of the nodes
- Username is admin
- Use the .pem key specified on instance creation
- Use the commands listed below to form a multi-node cluster by replacing the following with details specific to your QF2 in AWS instance
- NAME: Cluster name for your QF2 in AWS cluster
- PASSWORD: Your admin password
- PRIVATE_IP: List the VPC private IP addresses from all nodes (including the ssh'd node) that will be added to cluster in the commands below using a space to separate
Create a cluster
qq cluster_create --cluster-name NAME --admin-password PASSWORD --accept-eula --node-ips PRIVATE_IP
Add nodes to the cluster
qq node_add --node-ips PRIVATE_IP
NOTE: Orchestration tools can be utilized instead of qq commands to create multi-node clusters. Refer to Qumulo/Cloud Deployment Samples for additional details.
Running a clustered configuration of QF2 in AWS is recommended for workloads that require elasticity and have high performance demands. While QF2 in clustered configuration leverages erasure coding for data protection across nodes, coordinated failure of an AWS availability zone can still occur.
It is not recommended to run a QF2 cluster in AWS for production data without a replication or backup strategy.
You should now be able to successfully add nodes and create a multi-node cluster for QF2 in AWS
Like what you see? Share this article with your network!