Overview
You can manage GooseFS configuration groups through the GooseFS console on the cluster details page. For GooseFS cluster configuration practices, see GooseFS Cluster Configuration Practices. The following describes how to manage GooseFS cluster configuration groups in detail. Operation Steps
2. In the left navigation, click GooseFS Cluster List to enter the GooseFS cluster list page.
3. Select the GooseFS cluster that you want to manage, go to the cluster details page, select Configuration Group Management in the left sidebar, and enter the configuration group management page.
4. On the configuration group management page, you can manage the default cluster group or create a configuration group for management. GooseFS supports modifications to four types of configuration files. In the right side of the configuration group list, click Configuration Details to view the four types of configuration files. The following describes these configuration files:
goosefs-site.properties: GooseFS service configuration file, used to manage cluster data load, cache, and elimination policy configurations.
goosefs-env.sh: A dependent environment script file used to manage environment variables in the GooseFS cluster.
log4j.properties: The log output configuration for GooseFS service, used to manage various logs such as access logs, system logs, and monitoring information during operation.
core-site.xml: The underlying storage system configuration for GooseFS service coordination, used to manage the underlying storage systems connected to the GooseFS cluster, such as Cloud Object Storage (COS) and Cloud HDFS (CHDFS).
5. Click View Configuration on the right side of the configuration file, and then click Edit to modify the current configuration file. After editing, click Save to complete the configuration issuance.
6. The configuration will be distributed to all nodes in the cluster. After the configuration is distributed, you need to restart the service for it to take effect. Follow the pop-up prompt to go to the Task Center to view the execution results of tasks related to the configuration update.
Note:
After configuration issuance, it will overwrite the existing historical configuration. Rollback is temporarily not supported after overwriting. Proceed with caution.
After configuration issuance, you need to restart the service on the node management page. Observe whether the configuration takes effect after the service restart. If not, try re-issuing the configuration.
7. When releasing configurations for online services, you may need to configure grayscale settings node by node to observe whether the distributed configuration meets business expectations. GooseFS provides grayscale configuration capability. During the process of saving configurations, you can set grayscale batches and specify grayscale nodes for each batch.