What are the proper steps to reboot gluster gluster without data access downtime?

Solution Verified - Updated -

Issue

If for any reason there is a need to reboot the whole gluster cluster but no data access downtime is acceptable, simply follow the steps below. Following these steps will prevent healing issues, and in most cases, access to the data will not be impacted. There might be some delays after rebooting any one of the nodes, until the fuse client times-out, and switches over to another gluster node to access the volume(default timeout setting is 42 seconds).

Environment

  • Red Hat Gluster Storage 3.X

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content