Show Table of Contents
Chapter 6. Recommended Best Practices and Troubleshooting
- Enable the server side quorum at all times for the Red Hat Gluster Storage volumes hosting virtual machine images. For more information see Configuring Server-Side Quorum in the Red Hat Gluster Storage Administration Guide: https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/sect-Managing_Split-brain.html#sect-Preventing_Split-brain.
- Red Hat Gluster Storage Volumes that serve as Red Hat Enterprise Virtualization Master Storage Domain contain SANLocks and have the Red Hat Gluster Storage volume profile set to
virt. This enables the Client Side Quorum and avoids the inconsistency problems for Multiple Writer situations. For more information see Configuring Client-Side Quorum in the Red Hat Gluster Storage Administration Guide: https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/sect-Managing_Split-brain.html#sect-Preventing_Split-brain. - To reduce the risk of split-brain conditions developing in the cluster, Red Hat recommends using three-way replication when you create Red Hat Gluster Storage volumes. This involves setting
replica 3when creating replicate volumes, orreplica count 3when creating distributed-replicated volumes.
6.1. Troubleshooting the Integration
- Red Hat Gluster Storage 3.1 Volumes do not get mounted with Red Hat Enterprise Virtualization Hypervisor 3.3 and 3.4 versions as the glusterfs native clients available in those Hypervisors are not compatible with Red Hat Gluster Storage 3.1 servers.In order to make use of Red Hat Gluster Storage 3.1 volumes in Red Hat Enterprise Virtualization Hypervisor 3.3 and 3.4 versions, disable the readdir-ahead option on those volumes. This makes the volumes compatible with the older native client available with Red Hat Enterprise Virtualization Hypervisor 3.3 and 3.4.
# gluster volume set <vol> readdir-ahead off
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.