Overview

Method

Starting CM

# tbcm -b
CM Guard daemon started up.
import resources from '/cm/cmresource'...

TBCM 7.1.1 (Build 277758)TmaxTibero Corporation Copyright (c) 2020-. All rights reserved.Tibero cluster manager started up.
Local node name is (cm1:18629).

Enable CM Service Auto Restart - Service Auto Start Mode On

[root] # cmrctl act service --name [as service name]
Auto-boot mode is activated (tas)

[root] # cmrctl act service --name [db service name]
Auto-boot mode is activated (tac)


[root] # # cmrctl show
Resource List of Node cm1



=====================================================================
  CLUSTER     TYPE        NAME       STATUS           DETAIL         
----------- -------- -------------- -------- ------------------------
     COMMON  network           pub1       UP (public) ens160
     COMMON  network           int1       UP (private) 192.168.37.100/19629
     COMMON  cluster            cls       UP inc: int1, pub: pub1
        cls     file          cls:0       UP +0
        cls     file          cls:1       UP +1
        cls     file          cls:2       UP +2
        cls  service            tas       UP Active Storage, Active Cluster (auto-restart: ON)
        cls  service            tac       UP Database, Active Cluster (auto-restart: ON)
        cls       as           tas1 UP(NRML) tas, /db/tibero7, failed retry cnt: 0
        cls       db           tac1 UP(NRML) tac, /db/tibero7, failed retry cnt: 0
        cls      vip           vip1       UP tac, 192.168.56.11/255.255.255.0/192.168.56.255 (1)
                                             failed retry cnt: 0
        cls      vip           vip2    UP(R) tac, 192.168.56.21/255.255.255.0/192.168.56.255 (2)
                                             failed retry cnt: 0
=====================================================================

Check Service

[root] # cmrctl show service --name [as service name]
Service Resource Info
=================================================
Service name    : tas
Service type    : Active Storage
Service mode    : Active Cluster
Cluster         : cls
Inst. Auto Start: ON
Interrupt Status: COMMITTED
Incarnation No. : 2 / 2 (CUR / COMMIT)
=================================================
| INSTANCE LIST                                 |
|-----------------------------------------------|
| NID   NAME    Status  Intr Stat ACK No. Sched |
| --- -------- -------- --------- ------- ----- |
|   1      cm1 UP(NRML) COMMITTED       2     Y |
|   2      cm2 UP(NRML) COMMITTED       2     Y |
=================================================

[root] # cmrctl show service --name [db service name]
Service Resource Info
=================================================
Service name    : tac
Service type    : Database
Service mode    : Active Cluster
Cluster         : cls
Inst. Auto Start: ON
Interrupt Status: COMMITTED
Incarnation No. : 2 / 2 (CUR / COMMIT)
=================================================
| INSTANCE LIST                                 |
|-----------------------------------------------|
| NID   NAME    Status  Intr Stat ACK No. Sched |
| --- -------- -------- --------- ------- ----- |
|   1      cm1 UP(NRML) COMMITTED       2     Y |
|   2      cm2 UP(NRML) COMMITTED       2     Y |
=================================================

Test Method

After killing TAS / TAC processes or bringing TAS / TAC instances down, check if the status changes from BOOTING to UP using cmrctl show. The method is as follows: 

 [root] # kill -9 ps -ef|grep tbsvr_MGWP |grep -v grep|awk '{print $2}'

Note

When stopping RESOURCE in CM, the following message is displayed.

[root] # cmrctl stop db --name tac1
Cannot stop instance of service 'tac' manually (Auto-start mode is on)