Redundancy behavior of gluster replicated-distributed volume

Solution Verified - Updated -

Issue

  • Need confirmation about the client access behavior when multiple gluster node down.

    • Architecture
      4 nodes gluster running replicated-distributed volume

      N1 replicate to N2
      N3 replcate to N4
      N1/N3 distribute
      N2/N4 distribute

    • Client access behavior

      1. Shutdown any one node -> No impact
      2. Shutdown N1 and N3 -> No impact to fuse access from client
      3. Shutdown N2 and N4 -> No impact to fuse access from client
      4. Shutdown N1 and N2 -> Impact (unable to write to the fuse mounted share)
      5. Shutdown N3 and N4 -> Impact (unable to write to the fuse mounted share)

Environment

  • Red Hat Gluster Storage 3.2 and later

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