The steps to Rolling Restart Roles

When you run cmux rolling-restart-roles, you will always the folling steps.

1. Choose Cloudera Manager to rolling restart roles (only 1).

   Choose Cloudera Manager:
   
      Cloudera Manager Description  
    - ---------------- -------------
   >1 cm1              Test_Cluster1
    2 cm2              Test_Cluster2
   

2. Choose Cluster to rolling restart cluster (only 1).

   ROLLING RESTART HOSTS
   
     Choose Cluster:
   
     Cloudera Manager  Cluster  Cluster Display Name CDH Ver Secured Hosts
     ----------------- -------- -------------------- ------- ------- -----
     cm1               cluster2 cluster2               5.8.3       Y     9
     cm1               cluster3 cluster3               5.8.2       N     6
     cm1               cluster4 cluster4               5.8.3       Y     6
     cm1               cluster5 cluster5               5.7.0       N     5
     cm1               cluster6 cluster6               5.7.0       N     6
   > cm1               cluster  cluster1               5.3.8       N     1
     cm2               -        -                          -       N     3
     cm2               cluster  cluster1               5.4.9       Y     8
   

3. Choose the ROLE TYPE to rolling restart.

   ROLLING RESTART ROLES
     * Cloudera Manager : Test_Cluster1
   
   Choose the ROLE TYPE :
   
     Cluster Display Name Service Type Role Type
     -------------------- ------------ ------------------
   > cluster1             HBASE        REGIONSERVER
     cluster1             HBASE        MASTER
     cluster1             HDFS         NAMENODE
     cluster1             HDFS         DATANODE
    ...
   

4. Choose role(s) to rolling restart.

   ROLLING RESTART ROLES
     * Cloudera Manager : cm1
     * Cluster          : [cluster2] cluster1
     * Service type     : HBASE
     * Role type        : REGIONSERVER
   
   Choose ROLE(S) :
   
     Role Stype(short) Hostname Rolename
     ----------------- -------- ----------------------------------------------------
   > RS                host001  hbase1-REGIONSERVER-d334e1072927bbc0d358f23f1709fec5
   > RS                host002  hbase1-REGIONSERVER-644994c9bc653e6bd8f7608e2cdac99d
     RS                host003  hbase1-REGIONSERVER-3c0d7ef307bd9dff393f3253735fb07e
     RS                host004  hbase1-REGIONSERVER-5fe7c73fd4401c9a77af33c9d62c404f
   

   If you select NAMENODE, only nameservices for which HA is configured are displayed.

   ROLLING RESTART ROLES
     * Cloudera Manager : cm1
     * Cluster          : [cluster2] cluster1
     * Service type     : HDFS
     * Role type        : NAMENODe
   
   Choose Nameservice(s) :
   
     Name Service Active                      StandBy
     ------------ --------------------------- ---------------------------
   > test1        host001                     host002
   

5. Review your selection.

   ROLLING RESTART ROLES
   ---------------------------------------------------------------------------------
    * Cloudera Manager : cm1
    * Cluster          : [cluster1] cluster1
       ├── CDH Version : 5.4.9
       └── Secured     : Y
    * Service          : [HBASE] hbase1
       ├── Zookeeper   : zk001
       └── hbase-tool  : hbase-manager-0.98-1.4.1.jar
    * Role Type        : REGIONSERVER
    * Roles
       ├── [host001] hbase1-REGIONSERVER-c2da27bfb9b89d27d97c93fac04899c6
       └── [host002] hbase2-REGIONSERVER-644994c9bc653e6bd8f7608e2cdac99d
   ---------------------------------------------------------------------------------
   

   If REGIONSERVER is selected, display additional information for zookeeper leader and hbase-manager.

6. Confirm your selection.

   Are you sure you want to ROLLING RESTART on the above roles (y|n)?  y
   

7. Set seconds to sleep between each batch.

   Set SECONDS TO SLEEP between batches (>= 0 secs): 3
   

8. Set the max wait time after executing a roll RESTART command.

   Set the MAX WAIT TIME after executing the RESTART command (>= 180 secs): 180
   

9. Choose whether or not you run interactive mode.

   Do you want to proceed with INTERACTIVE MODE (y|n)? y
   

10. If you select

    NAMENODE: Path A. NAMENODE

    REGIONSERVER: Path B. REGIONSERVER

    JOURNALNODE: Path C. JOURNALNODE

    Other Services:

    (1) Enter a role level maintenance mode.

    Enter Maintenance Mode
    └── Maintenance owners: ["ROLE"]
    

    (2) Restart role.

    Restart hbase1-REGIONSERVER-d334e1072927bbc0d358f23f1709fec5
    Started
    

    (3) Exit maintenance mode.

    Exit Maintenance Mode
    └── Maintenance owners: []
    

11. Repeat these step if remained next batch.

12. If you select

    REGIONSERVER: Turn on HBase auto balancer using hbase-manager

    Do you want to turn on auto balancer (y|n)?  y
    Enable auto Balancer
    └── java -jar .../hbase-manager-1.2-1.4.1.jar assign zk001 balancer on  | tail -1
    Automatic balancer is turned on
    Finish