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
stunnel How To Encrypt Traffic to Redis with Stunnel on Ubuntu 16.04
Viewed 2757 times since Sun, Dec 6, 2020
Find All Large Files On A Linux System
Viewed 2810 times since Mon, Oct 29, 2018
How to schedule crontab in Unix Operating Systems
Viewed 2519 times since Fri, Jun 8, 2018
Learn Linux System Auditing with Auditd Tool on CentOS/RHEL
Viewed 5193 times since Fri, Apr 5, 2019
Linux – How to check the exit status of several piped commands
Viewed 3514 times since Wed, Jul 25, 2018
Logowanie za pomocą kluczy Secure Shell
Viewed 3490 times since Thu, May 24, 2018
Linux Find Large Files
Viewed 3499 times since Mon, Oct 29, 2018
bash mistakes This page is a compilation of common mistakes made by bash users. Each example is flawed in some way.
Viewed 9686 times since Sun, Dec 6, 2020
How To Use Systemctl to Manage Systemd Services and Units
Viewed 8164 times since Mon, Dec 7, 2020
RHEL: Crash kernel dumps configuration and analysis on RHEL 5
Viewed 8056 times since Sat, Jun 2, 2018