RHCS6: Basic operations on clustered services

RHCS: Basic operations on clustered services

# Tested on RHEL 6

# On a cluster like following one:

root@mynodeA:/#> clustat
Cluster Status for mycluster @ Thu Sep 25 21:39:54 2014
Member Status: Quorate

 Member Name                                          ID   Status
 ------ ----                                         ---- ------
 mynodeA                                               1  Online, Local, rgmanager
 mynodeB                                               2  Online, rgmanager

 Service Name                                         Owner (Last)   State
 ------- ----                                         ----- ------   -----
 service:myservice-1                                      mynodeA    started
 service:myservice-2                                      mynodeA    started
 service:myservice-3                                      mynodeB    started



# Stop a service ('-d' for "disable")
# ------------------------------------------------------------------------------------------

root@mynodeA:/#> clusvcadm -d myservice-2

root@mynodeA:/#> clustat
Cluster Status for mycluster @ Thu Sep 25 21:40:22 2014
Member Status: Quorate

 Member Name                                          ID   Status
 ------ ----                                         ---- ------
 mynodeA                                               1  Online, Local, rgmanager
 mynodeB                                               2  Online, rgmanager

 Service Name                                         Owner (Last)   State
 ------- ----                                         ----- ------   -----
 service:myservice-1                                      mynodeA    started
 service:myservice-2                                     (mynodeA)   disabled
 service:myservice-3                                      mynodeB    started



# Start a stopped service ('-e' for "enable")
# ------------------------------------------------------------------------------------------

# To be able to start a service it has to be in 'disabled' status. Sometimes the service
# may be in 'failed' status (neither 'started' nor 'disabled'), what means that there has
# been a problem with the service. In those cases, after solving the problems that
# potentially prevent the service from starting, we should run once again stop command,
# "clusvcadm -d" on the service in order to pass it to 'disabled' status.

# Obviously, when starting a service, we have to indicate on which node we want to start
# it ('-m' parameter)

root@mynodeA:/#> clusvcadm -e myservice-2 -m mynodeB

root@mynodeA:/#> clustat
Cluster Status for mycluster @ Thu Sep 25 21:45:17 2014
Member Status: Quorate

 Member Name                                          ID   Status
 ------ ----                                         ---- ------
 mynodeA                                               1  Online, Local, rgmanager
 mynodeB                                               2  Online, rgmanager

 Service Name                                         Owner (Last)   State
 ------- ----                                         ----- ------   -----
 service:myservice-1                                      mynodeA    started
 service:myservice-2                                      mynodeB    started
 service:myservice-3                                      mynodeB    started

# If service was in 'failed' status, first pass it to 'disabled'

root@mynodeA:/#> clustat
Cluster Status for mycluster @ Thu Sep 25 21:43:21 2014
Member Status: Quorate

 Member Name                                          ID   Status
 ------ ----                                         ---- ------
 mynodeA                                               1  Online, Local, rgmanager
 mynodeB                                               2  Online, rgmanager

 Service Name                                         Owner (Last)   State
 ------- ----                                         ----- ------   -----
 service:myservice-1                                      mynodeA    started
 service:myservice-2                                     (mynodeA)   failed
 service:myservice-3                                      mynodeB    started


root@mynodeA:/#> clusvcadm -d myservice-2


root@mynodeA:/#> clustat
Cluster Status for mycluster @ Thu Sep 25 21:44:01 2014
Member Status: Quorate

 Member Name                                          ID   Status
 ------ ----                                         ---- ------
 mynodeA                                               1  Online, Local, rgmanager
 mynodeB                                               2  Online, rgmanager

 Service Name                                         Owner (Last)   State
 ------- ----                                         ----- ------   -----
 service:myservice-1                                      mynodeA    started
 service:myservice-2                                     (mynodeA)   disabled
 service:myservice-3                                      mynodeB    started



# Switch a service to a different node ('-r' for "relocate")
# ------------------------------------------------------------------------------------------

# When starting a service, we have to indicate on which node we want to start
# it ('-r' parameter)


root@mynodeA:/#> clustat
Cluster Status for mycluster @ Thu Sep 25 21:45:17 2014
Member Status: Quorate

 Member Name                                          ID   Status
 ------ ----                                         ---- ------
 mynodeA                                               1  Online, Local, rgmanager
 mynodeB                                               2  Online, rgmanager

 Service Name                                         Owner (Last)   State
 ------- ----                                         ----- ------   -----
 service:myservice-1                                      mynodeA    started
 service:myservice-2                                      mynodeB    started
 service:myservice-3                                      mynodeB    started


root@mynodeA:/#> clusvcadm -r myservice-2 -m mynodeA


root@mynodeA:/#> clustat
Cluster Status for mycluster @ Thu Sep 25 21:49:29 2014
Member Status: Quorate

 Member Name                                          ID   Status
 ------ ----                                         ---- ------
 mynodeA                                               1  Online, Local, rgmanager
 mynodeB                                               2  Online, rgmanager

 Service Name                                         Owner (Last)   State
 ------- ----                                         ----- ------   -----
 service:myservice-1                                      mynodeA    started
 service:myservice-2                                      mynodeA    started
 service:myservice-3                                      mynodeB    started
0 (0)
Article Rating (No Votes)
Rate this article
Attachments
There are no attachments for this article.
Comments
There are no comments for this article. Be the first to post a comment.
Full Name
Email Address
Security Code Security Code
Related Articles RSS Feed
INSTALACJA MIB SNMP W SYSTEMIE CENTOS/RHEL 6
Viewed 13676 times since Fri, Nov 30, 2018
LVM: Reduce an existing Volume Group by removing one of its disks
Viewed 3126 times since Sat, Jun 2, 2018
List DNS records, nameservers of a domain from command line
Viewed 2686 times since Sun, Sep 30, 2018
Using stunnel and TinyProxy to obfuscate HTTP traffic
Viewed 8382 times since Fri, Sep 28, 2018
Manage Linux Password Expiration and Aging Using chage
Viewed 6158 times since Tue, Sep 11, 2018
How to manage Linux password expiry with the chage command
Viewed 12088 times since Tue, Sep 11, 2018
SYS: Configure a local repository. local repo
Viewed 11933 times since Mon, Oct 29, 2018
How to stop and disable auditd on RHEL 7
Viewed 42573 times since Tue, Aug 6, 2019
20 Linux Command Tips and Tricks That Will Save You A Lot of Time linux
Viewed 5858 times since Thu, Apr 18, 2019
How to remove CTRL-M (^M) characters from a file in Linux
Viewed 3549 times since Thu, Feb 7, 2019