Gluster geo-replication status is faulty

Solution Verified - Updated -

Issue

  • The status of geo-replication is always faulty.
[root@node1 ~]# gluster volume geo-replication vol test@node5::slavevol status

MASTER NODE    MASTER VOL    MASTER BRICK                               SLAVE USER    SLAVE                   SLAVE NODE    STATUS     CRAWL STATUS    LAST_SYNCED
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
node1          vol           /var/run/gluster/snaps/xxx/brick1/brick    test          test@node5::slavevol    N/A           Faulty     N/A             N/A
node2          vol           /var/run/gluster/snaps/xxx/brick2/brick    test          test@node5::slavevol    node5         Passive    N/A             N/A
node3          vol           /var/run/gluster/snaps/xxx/brick3/brick    test          test@node5::slavevol    N/A           Faulty     N/A             N/A
node4          vol           /var/run/gluster/snaps/xxx/brick4/brick    test          test@node5::slavevol    node5         Passive    N/A             N/A

Environment

  • Red Hat Gluster Storage 3.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.