Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
CentOS High Availability

You're reading from  CentOS High Availability

Product type Book
Published in Apr 2015
Publisher
ISBN-13 9781785282485
Pages 174 pages
Edition 1st Edition
Languages
Toc

Table of Contents (21) Chapters close

CentOS High Availability
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Getting Started with High Availability 2. Meet the Cluster Stack on CentOS 3. Cluster Stack Software on CentOS 6 4. Resource Manager on CentOS 6 5. Playing with Cluster Nodes on CentOS 6 6. Fencing on CentOS 6 7. Testing Failover on CentOS 6 8. Two-node Cluster Considerations on CentOS 6 9. Cluster Stack Software on CentOS 7 10. Resource Manager on CentOS 7 11. Playing with Cluster Nodes on CentOS 7 12. STONITH on CentOS 7 13. Testing Failover on CentOS 7 14. Two-node Cluster Considerations on CentOS 7 Index

Removing a cluster node


Shutting down a cluster node is one way to disable it, but you must also learn how to remove a cluster node from a running cluster configuration. Removing a cluster node from a cluster configuration does not require cluster service downtime, unless the cluster service is running on the cluster node you would like to remove.

Tip

Before you start the procedure of removing a cluster node from the cluster configuration, make sure that no cluster resources and services are running on the node.

You can remove a cluster node from an existing configuration by following these steps:

  1. Remove the cluster node from Corosync: Edit the corosync.conf configuration file on all cluster nodes and remove the desired cluster node from the nodelist section. You can download an example cluster node corosync.conf configuration file, where the node-4.geekpeek.net cluster node was removed from the cluster configuration, from the corosync-conf-2.txt file in the code bundle.

    Note

    Remember to remove...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €14.99/month. Cancel anytime