No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionInsight HD 6.5.0 Administrator Guide 02

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Starting, Stopping, and Restarting a Service

Starting, Stopping, and Restarting a Service

Scenarios

You can perform the following maintenance operations on a service on FusionInsight Manager:

  • Start a specified service in the cluster.
  • Stop a specified service in the cluster.
  • Restart a specified service in the cluster.

You can perform related operations on the FusionInsight Manager service management page or service details page. This section describes how to start, stop, and restart a service on the service management page in the tile view mode.

Starting a Service

  1. Log in to FusionInsight Manager.
  2. Choose Cluster > Service.
  3. In the area where the stopped service resides, click in the upper right corner.
  4. Choose Start from the displayed shortcut menu.

    In the confirmation dialog box, click OK to start the current service.

Stopping a Service

  1. Log in to FusionInsight Manager.
  2. Choose Cluster > Service.
  3. In the area where the normal service resides, click in the upper right corner.
  4. Choose Stop from the displayed shortcut menu.
  5. In the displayed dialog box, enter the password of the current login user and click OK.
  6. In the confirmation dialog box, click OK.

    Stopping a service on which other services depend will cause unavailability of those services. In this case, select Stop upper-layer services. Determine whether to perform the operation based on the information displayed.

Restarting a Service

  1. Log in to FusionInsight Manager.
  2. Choose Cluster > Service.
  3. In the area where the normal service resides, click in the upper right corner.
  4. Choose Restart from the displayed shortcut menu.
  5. In the displayed dialog box, enter the password of the current login user and click OK.
  6. In the displayed confirmation dialog box, click OK.

    Restarting a service on which other services depend causes unavailability of those services. In this case, select Restart upper-layer services. Determine whether to perform the operation based on the information displayed. Services in the cluster are restarted one by one due to their dependencies. Table 3-3 lists the restart duration of a single service.

    Table 3-3 Restart time

    Service Name

    Restart Duration

    Start Duration

    Remarks

    HDFS

    10 min+x

    NameNode: 4 min+x

    DataNode: 2 min

    JournalNode: 2 min

    Zkfc: 2 min

    X indicates the duration for loading NameNode metadata. About two minutes are required for each ten million files. For example, if there are 50 million files, x indicates 10 minutes. The start duration is affected by the duration for DataNode to report data blocks.

    Yarn

    5 min + x

    ResourceManager: 3 min + x

    NodeManager: 2 min

    x indicates the time corresponding to the number of reserved tasks that need to be restored by ResourceManager. Each 10 thousand reserved tasks require one minute.

    MapReduce

    2 min + x

    JobHistoryServer: 2 min + x

    x indicates the scanning duration of historical tasks. Each 100 thousand tasks take about 2.5 minutes.

    Zookeeper

    2 min + x

    Quorumpeer: 2 min + x

    x indicates the duration for loading Znodes. Each one million Znodes take about one minute.

    Solr

    10min+x

    10min+x

    X indicates the duration for restoring data. About ten minutes are required for each 10 thousand shards. Assuming that there are 150 instances, extra 15 minutes are required to restore data if data volume of each 10 thousand shards increases by 15 TB.

    Elasticsearch

    10 min+x

    5 min+x

    X indicates the duration for restoring data. About eight minutes are required for each 10 thousand shards.

    Hive

    3.5 min

    HiveServer: 3 min

    MetaStore: 90s

    Webhcat: 1 min

    Hiveoverall service: 3 min

    -

    Spark/Spark2x

    5 min

    JobHistory: 5 min

    SparkResource: 5 min

    JDBCServer: 5 min

    -

    Graphbase

    4min

    GraphServer : 3min

    LoadBalancer : 1min

    -

    Flink

    1min

    FlinkRource: 1min

    -

    Kafka

    2 min + x

    Broker: 1 min + x

    KafkaUI: 1 min

    X indicates the data recovery duration. It takes about two minutes to start a single instance with 20000 partitions.

    Storm/Streaming

    6 min

    Nimbus: 3 min

    UI: 1 min

    Supervisor: 1 min

    Logviewer: 1 min

    -

    Redis

    1 min + x

    Redis: 1 min + x

    1. 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.
    2. X indicates the data recovery duration. It takes about two minutes to restore 1 GB data of a single instance from the RDB. It takes about one minute to restore 1 GB data of a single instance from the AOF.

    FTP-Server

    1 min

    FTP-Server: 1 min

    -

    Flume

    3 min

    Flume: 2 min

    MonitorServer: 1 min

    -

    Elk

    10min

    ElkServer: 10min

    -

Download
Updated: 2019-05-17

Document ID: EDOC1100074522

Views: 6100

Downloads: 12

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next