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
Check a Website Availability from the Linux Command Line
Viewed 6687 times since Mon, Feb 18, 2019
RHEL : How to deal with “CLOSE_WAIT” and “TIME_WAIT” connection
Viewed 26125 times since Thu, Feb 14, 2019
LVM: Extend an existing Volume Group by adding a new disk
Viewed 2101 times since Sat, Jun 2, 2018
How To Add Swap Space on Ubuntu 16.04
Viewed 2382 times since Fri, Jun 8, 2018
HowTo: Kill TCP Connections in CLOSE_WAIT State
Viewed 15835 times since Thu, Feb 14, 2019
KONTO SFTP Z CHROOTEM Z UŻYCIEM OPENSSH-SERVER NA CENTOS/RHEL6
Viewed 1863 times since Fri, Nov 30, 2018
Szybkie sprawdzenie zewnętrznego adresu IP i hosta
Viewed 3404 times since Thu, May 24, 2018
RHEL: Back-up/Replicate a partition table
Viewed 3454 times since Sun, May 27, 2018
sed Delete / Remove ^M Carriage Return (Line Feed / CRLF) on Linux or Unix
Viewed 10308 times since Thu, Feb 7, 2019
Linux Proxy Server Settings – Set Proxy For Command Line
Viewed 3549 times since Mon, Feb 18, 2019