Restarting and Maintaining Components

Last updated: 2020-05-28 17:59:30

    Operation Scenarios

    The component management feature enables restart at the component level and component adding. With advanced management, you can perform operations at the component service and node levels such as restart, pause, and maintenance.

    Definitions

    • Restart: the selected components and services will be restarted on a rolling basis by node.
    • Add Component: you can use this feature to add components that were not selected when you created the cluster in the current version.
    • Pause: the services in the selected node will be paused, which can then be resumed by using the Start feature.
    • Maintenance: the process daemon will be stopped for the services on the selected node. When a process becomes exceptional for various reasons, no alarming or automatic recovery will occur. This is suitable for node debugging. You can use the Exit Maintenance feature to resume the daemon.

    Directions

    Log in to the EMR Console and enter the Component Management page, where you can perform operations such as Add Component, Restart Component, and Reset Native UI Password. Select Operation > Configure for a component to enter its service/node-level management page.

    Adding component

    Existing components in the cluster are selected by default and cannot be canceled. You can only add components that are currently not installed in the cluster.

    Restarting component

    You can restart components in the console, and rolling restart is checked by default. Note: if rolling restart is disabled, all nodes will be restarted at the same time, and the services may become unavailable. Please do so with caution.
    There are two policies for failure-handling when node restart fails: waiting for processing in case of failure or continuing processing in case of single node failure.

    The restart methods supported by the service components are as follows:

    Component Service Restart Mode Description Remarks
    HDFS NameNode Quick restart mode It can be restarted by running `hadoop-daemon.sh stop | start namenode` -
    NameNode Safe restart mode
  • For an HA cluster, run `saveNameSpace` on the standby NameNode. Then, restart the component by running `hadoop-daemon.sh stop | start namenode`
  • For a non-HA cluster, the quick restart mode is used
  • Only rolling restart is supported
    DataNode Default restart mode It can be restarted by running `hadoop-daemon.sh stop | start datanode` -
    JournalNode Default restart mode It can be restarted by running `hadoop-daemon.sh stop | start journalnode` -
    zkfc Default restart mode It can be restarted by running `hadoop-daemon.sh stop | start zkfc` -
    YARN ResourceManager Default restart mode It can be restarted by running `sbin/yarn-daemon.sh stop | start resourcemanager` Only rolling restart is supported
    NodeManager Default restart mode It can be restarted by running `sbin/yarn-daemon.sh stop | start nodemanager` -
    JobHisotryServer Default restart mode It can be restarted by running `sbin/yarn-daemon.sh stop| start historyserver` -
    TimeLineServer Default restart mode It can be restarted by running `sbin/yarn-daemon.sh stop | start timelineserver` -
    HBASE HbaseThrift Default restart mode It can be restarted by running `hbase-daemon.sh stop | start thrift` -
    HMaster Default restart mode It can be restarted by running `hbase-daemon.sh stop | start master` -
    HRegionServer Quick restart mode It can be restarted by running `hbase-daemon.sh stop | start regionserver` -
    HRegionServer Safe restart mode It can be restarted by running `graceful_stop.sh --restart --reload` -
    HIVE HiveMetaStore Default restart mode It can be restarted by running `hcat_server.sh stop | strat` -
    HiveServer2 Default restart mode It can be restarted by running `hive-daemon.sh stop-h2 | start-h2` -
    HiveWebHcat Default restart mode It can be restarted by running `webhcat_server.sh stop | start` -
    PRESTO PrestoCoordinator Default restart mode It can be restarted by running `bin/launcher stop | start` Only rolling restart is supported
    PrestoWorker Default restart mode It can be restarted by running `bin/launcher stop | start` -
    ZooKeeper QuorumPeerMain Default restart mode It can be restarted by running `bin/zkServer.sh stop | start` -
    Spark SparkJobHistoryServer Default restart mode It can be restarted by running `sbin/stop-history-server.sh | sbin/start-history-server.sh` -
    Hue Hue Default restart mode It can be restarted by running `build/env/bin/start.sh` and `build/env/bin/sop.sh` -
    Oozie Oozie Default restart mode It can be restarted by running `oozied.sh stop | start` -
    Storm Nimbus Default restart mode It can be restarted by running `bin/storm-daemon.sh nimbus stop | start` -
    Supervisor Default restart mode It can be restarted by running `bin/storm-daemon.sh supervisor stop | start` -
    LogViewer Default restart mode It can be restarted by running `bin/storm-daemon.sh nimbus stop | start` -
    UI Default restart mode It can be restarted by running `bin/storm-daemon.sh nimbus stop | start` -
    Ranger Ranger Default restart mode It can be restarted by running `sbin/ranger-daemon.sh stop | start` -
    Alluxio AlluxioMaster Default restart mode It can be restarted by running `bin/alluxio-stop.sh master` and `bin/alluxio-start.sh master` -
    AlluxioWorker Default restart mode It can be restarted by running `bin/alluxio-stop.sh worker` and `bin/alluxio-start.sh worker` -
    Ganglia Httpd Default restart mode It can be restarted by running `/sbin/service http stop | start` -
    gmetad Default restart mode It can be restarted by running `/sbin/service gmetad stop | start` -
    gmond Default restart mode It can be restarted by running `/sbin/service gmon stop | start` -

    Role management

    The Service Status column displays whether the current service is running or paused, and the Maintenance Status column displays whether the current service is under maintenance.

    Was this page helpful?

    Was this page helpful?

    • Not at all
    • Not very helpful
    • Somewhat helpful
    • Very helpful
    • Extremely helpful
    Send Feedback
    Help