Overview

Updated on 2024-11-29 GMT+08:00

View PDF

Dashboard

Log in to FusionInsight Manager and choose Cluster > Services. The service management page is displayed, including the functional area and service list.

Functional Area

In the functional area of the service management page, you can select a view type and filter and search for services by service type. You can use the advanced search to select required services based on the running status and configuration status.

Service List

The service list on the service management page contains all installed services in the cluster. If the tile view is selected, the services will be displayed in pane style. If you select the list view, the services will be displayed in a table.

NOTE:

In this section, the Tile View is used by default.

The service list displays the running status, configuration status, role type, and number of instances of each service. On this page, you can perform some service maintenance tasks, such as starting, stopping, and restarting services.

**Table 1** Service running status
Status	Description
Normal	Indicates that the service is running properly.
Faulty	Indicates that the service cannot run properly.
Partially Healthy	Indicates that some enhanced functions of the service are abnormal.
Not started	Indicates that the service is stopped.
Unknown	Indicates that the initial status of the service cannot be detected.
Starting	Indicates that the service is being started.
Stopping	Indicates that the service is being stopped.
Failed to start	Indicates that the service fails to be started.
Failed to stop	Indicates that the service fails to be stopped.

NOTE:

If the running status of a service is Faulty, an alarm is generated. Rectify the fault based on the alarm information.
HBase, Hive, Spark, and Loader may be in the Subhealthy state.
- If Yarn is installed but is abnormal, HBase is in the Subhealthy state. If the multi-instance function is enabled, all installed HBase service instances are in the Subhealthy state.
- If HBase is installed but is abnormal, Hive, Spark, and Loader are in the Subhealthy state.
- If any HBase instance is installed but is abnormal after the multi-instance function is enabled, Loader is in the Subhealthy state.
- If an HBase instance is installed but is abnormal after the multi-instance function is enabled, the Hive and Spark instances that map to the HBase instance are in the Subhealthy state. That is, if HBase 2 is installed but is abnormal, Hive 2 and Spark2 are in the Subhealthy state.

**Table 2** Service configuration status
Status	Description
Synchronized	Indicates that all service parameter settings have taken effect in the cluster.
Expired	Indicates that the latest configuration is not synchronized and does not take effect after the service parameters are modified. You need to synchronize the configurations and restart the services. You can click next to Configuration Status to view expired configuration items.
Failed	Indicates that a communication or read/write exception occurs during the parameter configuration synchronization. Use Synchronize Configuration to rectify the fault.
Synchronizing	Indicates that the service parameter configuration is being synchronized.
Unknown	Indicates that the initial status of the service cannot be detected.

You can click a service in the service list to perform simple maintenance and management operations on the service, as described in Table 3.

**Table 3** Basic maintenance and management
Menu Item on the UI	Description
Start Service	Start a specified service in the cluster.
Stop Service	Stop a specified service in the cluster.
Restart Service	Restart a specified service in the cluster. NOTE: If a service is restarted, other services that depend on this service will be unavailable. Therefore, select Restart upper-layer services. Determine whether to perform this operation based on the displayed service list. Services are restarted one by one due to their dependency. Table 4 describes the restart duration of a single service.
Service Rolling Restart	Restart a specified service in the cluster without interrupting services. For details about the parameter settings, see Table 1.
Synchronize Configuration	Enable new configuration parameters for a specified service in the cluster. Distribute new configuration parameters for services whose Configuration Status is Expired. NOTE: After some services are synchronized, restart the services for the settings to take effect.

**Table 4** Restart duration
Service	Restart Duration	Startup Duration	Remarks
IoTDB	3 min + x	ConfigNode: 2 min IoTDBServer: 1 min + x	x indicates the metadata loading duration of each IoTDBServer instance. It takes about 3 seconds to load 200 GB data. The restart duration is calculated separately when all instances are started at the same time. The service's total restart time depends on the size of the data on the node that has the most data.
CDL	2 min	CDLConnector: 1 min CDLService: 1 min	-
ClickHouse	4 min	ClickHouseServer: 2 min ClickHouseBalancer: 2 min	-
HDFS	10min+x	NameNode: 4 min + x DataNode: 2 min JournalNode: 2 min Zkfc: 2 min	x indicates the NameNode metadata loading duration. It takes about 2 minutes to load 10,000,000 files. For example, x is 10 minutes for 50 million files. The startup duration fluctuates with reporting of DataNode data blocks.
Yarn	5 min + x	ResourceManager: 3 min + x NodeManager: 2 min	x indicates the time required for restoring ResourceManager reserved tasks. It takes about 1 minute to restore 10,000 reserved tasks.
MapReduce	2 min + x	JobHistoryServer: 2 min + x	x indicates the scanning duration of historical tasks. It takes about 2.5 minutes to scan 100,000 tasks.
ZooKeeper	2 min + x	quorumpeer: 2 min + x	x indicates the duration for loading znodes. It takes about 1 minute to load 1 million znodes.
Solr	10 min + x	10 min + x	x indicates the data restoration duration. It takes about 10 minutes to restore data of 10,000 shards. For example, if there are 150 instances and the data volume increases by 15 TB for every 10,000 shards, the data restoration duration increases by about 15 minutes.
Elasticsearch	10 min + x	5 min + x	x indicates the data restoration duration. It takes about 8 minutes to restore data of 10,000 shards.
Hive	3.5 min	HiveServer: 3 min MetaStore: 1 min 30s WebHcat: 1 min Hive service: 3 min	-
Spark	5 min	JobHistory: 5 min SparkResource: 5 min JDBCServer: 5 min	-
Flink	4 min	FlinkResource: 1 min FlinkServer: 3 min	-
Kafka	2 min + x	Broker: 1 min + x	x indicates the data restoration duration. It takes about 2 minutes to start 20,000 partitions for a single instance.
Redis	1 min + x	Redis: 1 min + x	The number of instances installed on a single Redis node depends on the number of CPU cores. It takes about one minute to start a single instance. x indicates the data restoration duration. It takes about 2 minutes to restore 1 GB data of a single instance from the RDB. It takes about 1 minute to restore 1 GB data of a single instance from AOF.
FTP-Server	1 min	FTP-Server: 1 min	-
Flume	3 min	Flume: 2 min MonitorServer: 1 min	-
RTDService	2 min	RTDServer: 2 min	-
Containers	2 min	WebContainer: 2 min	-
MOTService	30 min	MOTServer:30 min	-
Doris	2 min	FE: 1min BE: 1min DBroker: 1min	-
MemArtsCC	2 min	CCWorker: 1min CCSideCar: 1min	-