tencent cloud

Creating a GooseFS Cluster
Last updated:2025-07-17 17:42:50
Creating a GooseFS Cluster
Last updated: 2025-07-17 17:42:50

Overview

You can create a GooseFS cluster on the GooseFS list page through the GooseFS console. For the concept of GooseFS cluster, please see GooseFS Cluster Overview. The following is a detailed introduction on how to create a GooseFS cluster.
Note:
The GooseFS cluster has a regional concept. Generally, it is recommended to prioritize deployment in the same region where your computing services reside. For example, if big data analytics jobs are in Guangzhou Zone 6, the GooseFS cluster should also be deployed in Guangzhou Zone 6 to minimize data IO paths.

Prerequisites

Before logging in to the console to use GooseFS, you need to contact us to enable the GooseFS service.

Directions

2. In the left navigation, select GooseFS > Instance List to enter the GooseFS Cluster List Page.
3. Click Create to enter the GooseFS cluster creation process. The creation process of a GooseFS cluster mainly consists of three main steps: configuring cluster information, configuring cluster resources, and confirming information.
4. Cluster information is primarily used to describe the basic attributes of a GooseFS cluster. The following parameters need to be configured.



Cluster Name: Cluster unique identifier, globally unique under the account. The cluster name must follow the naming specification. For details, refer to the description in the GooseFS cluster overview.
Cluster Description: Used to describe the attributes, purpose, and other information of the cluster.
Cluster Category: Different types or application scenarios of clusters. Divided into Tencent Public Cloud clusters and IDC cloud clusters.
Region: The region where the cluster is located, generally matching the region of the computing service's located cluster.
Availability Zone: The availability zone 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 situations.
Subnet: The subnet where the cluster is located.
Tag: Cluster tag information.
5. Cluster resources are primarily used for configuring the cache storage scale that GooseFS clusters need to manage. GooseFS deployment modes include Fully Managed Hosting, Master-Only Hosting, and Management Plane Hosting three modes. The following explains the cluster creation for each mode.
Fully Managed Hosting
Master-Only Hosting
Management Plane Hosting
In Fully Managed Hosting 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.

In Fully Managed Hosting mode, users only need to select instance capacity (10TB-1000TB, step length 10TB).

In Master-Only Hosting mode, users purchase Master instances on the GooseFS platform; Worker nodes require users to purchase CVM instances as nodes, which are added to the cluster via Node Management after cluster creation. When creating a GooseFS cluster in Master-Only Hosting mode, the parameter descriptions are as follows:



Deployment Mode: Select Master-managed.
Master Specification: You can choose Medium edition, Large edition, or XLarge edition.
The specifications for different Master node types are as follows:
Model specification
Number of Files
Medium
100 million
Large
5 billion to 7 billion
XLarge
10 billion to 12 billion
Instance Type: Select CVM/EMR.
Cache Configuration
Cache Path: The storage path for GooseFS cluster Worker node data on the host machine.
Cache Capacity: Data capacity of a single Worker node in the cluster.
In Management Plane Hosting mode, both the Master and Worker nodes of GooseFS require users to purchase CVM instances as nodes. When creating a GooseFS cluster in managed control plane mode, the relevant parameter descriptions are as follows:
Deployment Mode: Select management plane-managed.
Type: Currently supports CVM/EMR.
Instance Version: GooseFS version number information.
High Availability Mode: If enabled, a minimum of 3 Master nodes must be deployed.
Master Node: Select a Master node. If high availability mode is not enabled, only 1 Master node is required.
Worker Node: Select a worker node.
Master Formatted Mounting: Used for formatting the disk and setting up the file system mount point. Users can choose whether to perform the formatted mounting. If not enabled, there is no need to set the data disk mounting option during the creation flow; it can be mounted manually or using scripts. If enabled, parameters such as device name, format system, and mount point need to be filled in.
Mounted Device Name: The hardware device that needs to be mounted, usually a specific disk partition. You need to log in to the machine to view it, typically located in the /dev path.
Format System: Linux file system type.
Mount Point: File system mount point.
Example:
If you need to format the device /dev/vdb to ext4 and mount it to the /var/lib/docker directory, you can set it up as follows: Device name /dev/vdb, File system type ext4, Mount point /var/lib/docker.
Worker Formatted Mounting: Configuration instructions are the same as the above Master formatted mounting.
Cache Configuration: Mainly used for configuring Worker nodes.
<Cache path>: The storage path for GooseFS cluster Worker node data on the host machine.
<Cache storage capacity>: Data capacity of a single Worker node in the GooseFS cluster.
Mount Point Configuration: Primarily used to set detailed configuration information for mount points, with single-disk cache capacity being the most critical.
<Journal Path>: The storage path for GooseFS cluster Journal logs on the host machine.
Block Path: The storage path for GooseFS cluster's Block metadata on the host.
Metastore Path: The storage path of GooseFS cluster's metadata on the host machine.
6. After entering the above parameters as required, click Next, and the system will start checking node status. After the system check is correct, click Confirm to execute.
7. Enter the cluster creation process. You can view the detailed progress of cluster deployment in the Task Center.

Following Steps

After creating the GooseFS cluster, you can log in to the cluster according to business needs to proceed to the next step for node management, namespace management, client management, configuration management, and other operations. For specific operations, refer to the following document:
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No

Feedback