Introduction
You can create a GooseFS cluster on the GooseFS list page through the GooseFS console. For the concept of GooseFS clusters, see GooseFS Cluster Overview. The following describes in detail how to create a GooseFS cluster. Attention:
GooseFS clusters are region-specific. In general, it is recommended that you deploy a GooseFS cluster in the same region as your computing business. For example, if your big data analytics jobs run in Guangzhou Zone 6, it is recommended that you also deploy the GooseFS cluster in Guangzhou Zone 6 to shorten the data I/O path.
Prerequisites
Before using GooseFS in the console, contact us to activate the GooseFS service. If the service is already activated, you can skip this step. Operation Steps
2. In the left navigation, choose GooseFS > Instance List to enter the GooseFS cluster list page.
3. Click Create to go to the cluster creation flow. The GooseFS cluster creation flow consists of three main steps: configuring cluster information, configuring cluster resources, and confirming the information.
Cluster Information: Used to describe the basic attributes of a GooseFS cluster. The configuration items are described as follows.
Cluster Name: Cluster unique identifier, globally unique under the account. Enter 1 to 50 characters, supporting a combination of uppercase and lowercase letters, Chinese characters, digits, underscores (_), periods (.), and spaces.
Cluster Description: Used to describe the attributes, purpose, and other information of the cluster.
Cluster Category: Tencent Public Cloud clusters.
Region: The region where the cluster is located, generally consistent with the region of the cluster where the computing business resides.
AZ: The AZ where the cluster is located, generally the same AZ as the computing cluster.
VPC: The VPC where the cluster is located, generally the same VPC as the computing cluster. Try to avoid cross-VPC deployment.
Subnet: The subnet where the cluster is located.
Tag: Cluster tag information.
Cluster Resources: Used to configure the cache storage capacity that the GooseFS cluster needs to manage. The configuration items are described as follows.
Deployment Mode: Select the Fully Managed Hosting Mode. In this mode, users do not need to self-purchase Master nodes and Worker nodes. All nodes are hosted by Tencent Cloud. The Tencent Cloud team is responsible for the overall availability and stability of the cluster, ensuring users can focus on core business. The configuration items are described as follows:
Replica Quantity: You can select one, two, or three replicas, corresponding to data reliability of 99%, 99.999%, and 99.9999999% (nine 9s), respectively. If you need to use one replica, please contact us. Attention:
After the cluster is created, the replica quantity configuration cannot be hot-switched. To modify the replica quantity, disable the write cache and then re-enable it with the specified replica quantity.
Total Instance Capacity: Total instance capacity = read cache capacity + write cache capacity. In an instance, read and write cache capacities are used for read and write scenarios. The read and write cache capacity can be selected from 10TB to 1000TB in increments of 10TB. The total capacity scales in multiples of 10TB, and a larger capacity provides higher total bandwidth.
Single replica: With a step size of 10TB, it can provide a peak read bandwidth of 2GBps and a peak write bandwidth of 1.4GBps. Note: These peak bandwidths refer to actual physical bandwidth.
Two replicas: With a step size of 20TB, it can provide a peak read bandwidth of 4GBps and a peak write bandwidth of 2.8GBps. Note: These peak bandwidths refer to actual physical bandwidth.
Three replicas: With a step size of 30TB, it can provide a peak read bandwidth of 6GBps and a peak write bandwidth of 4.2GBps. Note: These peak bandwidths refer to actual physical bandwidth.
Note:
This capacity is the actual disk capacity, and the actual cacheable business capacity depends on the number of write replicas. For example, if you purchase 30TB of write cache capacity, the actual cacheable business capacity is 15TB when two replicas are selected, and 10TB when three replicas are selected.
Correspondingly, the peak throughput provided by the write cache is also related to the number of replicas. By default, the write cache provides a peak throughput of 140MBps/TB. When two replicas are selected, the available peak business bandwidth is 70MBps/TB.
After the cluster is created, you can scale down the write cache capacity or disable the write cache. During the scale-down or disabling process, the scaled-down capacity is locked and cannot be written to. After the cached data is persisted, the capacity is released.
Instance Fee: Confirm that the instance fee is correct. The instance fee is calculated based on the total instance capacity.
Terms of Service: Select the terms of service.
Confirmation Information
After filling in the required parameters, click Next to start checking the node status. After the system check is successful, click OK to execute. You will then enter the cluster creation flow, where you can view the detailed progress of cluster deployment in the Task Center.
Following Steps
After creating a GooseFS cluster, you can log in to the cluster as needed for subsequent operations such as node management, namespace management, client management, and configuration management. For detailed instructions, refer to the following documents: