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

Hardware failure


If your cluster node experiences a CPU, RAM, or motherboard failure, it is an unrecoverable failure and the cluster node will go offline. The cluster fencing mechanism will try to fence the problematic cluster node anyway, making sure it is not accessing the cluster's shared storage, which could lead to cluster data corruption. If your cluster node experiences disk failure, it should not affect the cluster node operation due to RAID disk redundancy, which enables normal cluster operation.

The cluster from the following example is configured to provide a webserver cluster service that includes a cluster IP address and an Apache webserver instance. The webserver cluster service is running on the node-1 cluster node. In the following screenshot, you can see the current state of the cluster:

You can proceed to simulate hardware failure on the part of the node-1 cluster node. This can be done by cutting off the power to the cluster node.

Once the cluster node is powered off, check...

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