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
Manage Linux Password Expiration and Aging Using chage
Viewed 4721 times since Tue, Sep 11, 2018
How to Synchronize Directories Using Lsyncd in Linux
Viewed 13984 times since Wed, Oct 31, 2018
Odpalenie polecenia tylko na jedną godzinę
Viewed 2908 times since Thu, May 24, 2018
Linux: Disks diagnostic using smartctl
Viewed 15192 times since Wed, Jul 25, 2018
Linux – Securing your important files with XFS extendend attributes
Viewed 7608 times since Wed, Jul 25, 2018
ubuntu How to Reset Forgotten Passwords in Ubuntu 16.04
Viewed 3495 times since Tue, Dec 8, 2020
Linux - How to shutdown or reboot
Viewed 2223 times since Fri, Jun 8, 2018
Fix rpmdb: Thread died in Berkeley DB library
Viewed 21192 times since Fri, Feb 14, 2020
www.unixarena.com
Viewed 2513 times since Fri, Jul 27, 2018
RHEL: How to change a USER/GROUP UID/GID and all owned files
Viewed 22903 times since Sat, Jun 2, 2018