The service management capability provides a GUI for operating GooseFS clusters, supporting maintenance operations like service updates, enablement, termination, isolation, and lifting isolation. Currently, GooseFS clusters support the following service categories:
1. Master service: The Master service primarily provides metadata management capabilities. When users read or write files, they can obtain file metadata through the Master service to access file data blocks.
2. Worker service: The Worker service primarily stores Block data. After obtaining file metadata, users access the corresponding Worker service nodes to retrieve data based on the Block data information disclosed in the metadata.
3. Fuse service: The Fuse service provides a file system client for businesses. Businesses can access files on GooseFS through the GooseFS Fuse client using file protocols.
4. Job Master service: The Job Master service manages tasks on a GooseFS cluster, such as metadata loading (LoadMetadata), preheating (DistributedLoad), and metadata eviction (TTL).
5. Job Service: The Job Worker service executes tasks on a GooseFS cluster and is managed by the Job Master service.
Operation Instructions
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 Service Management in the left sidebar, and enter the service management page.
4. On the service management page, after selecting a service, you can perform the corresponding operations:
Update: Updates the keepalive status of a service, which can be used to enable or disable the service keepalive capability on a node. When the keepalive capability is enabled, the system automatically attempts to restart the service if the node becomes abnormal.
Enable: Enables the service on a node. Services on abnormal nodes or nodes with suspended services can be restarted through this operation.
Stop: Can be used to suspend services on a node for temporary troubleshooting.
Restart: Can be used to restart services on nodes for effective configuration.
Isolation: Can be used to isolate abnormal nodes from the cluster. For example, when the Worker service is abnormal, the node is isolated from the cluster to prevent traffic from being routed to the abnormal node.
Cancel Isolation: Can be used to rejoin services on nodes that have restored health to the cluster.