[Bugs] [Bug 1218586] New: dist-geo-rep : all the bricks of a node shows faulty in status if slave node to which atleast one of the brick connected goes down.

bugzilla at redhat.com bugzilla at redhat.com
Tue May 5 10:11:43 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1218586

            Bug ID: 1218586
           Summary: dist-geo-rep : all the bricks of a node shows faulty
                    in status if slave node to which atleast one of the
                    brick connected goes down.
           Product: GlusterFS
           Version: 3.7.0
         Component: geo-replication
          Severity: high
          Priority: high
          Assignee: bugs at gluster.org
          Reporter: avishwan at redhat.com
                CC: aavati at redhat.com, avishwan at redhat.com,
                    bugs at gluster.org, csaba at redhat.com,
                    david.macdonald at redhat.com, gluster-bugs at redhat.com,
                    nlevinki at redhat.com, nsathyan at redhat.com,
                    storage-qa-internal at redhat.com, vkoppad at redhat.com
        Depends On: 1064309, 1212410



+++ This bug was initially created as a clone of Bug #1212410 +++

+++ This bug was initially created as a clone of Bug #1064309 +++

Description of problem:  all the bricks of a node shows faulty in status if
slave node to which atleast one of the brick connected goes down. If a node has
3 bricks, and if one of the slave node goes down. If out of those 3 bricks,
atleast one is connected to that node on slave, then status for all the bricks
also goes to faulty. 


Version-Release number of selected component (if
applicable):glusterfs-3.4.0.59rhs-1


How reproducible: happens everytime.


Steps to Reproduce:
1. create and start a geo-rep relationship between master(6x2 with 4 nodes) and
slave( 6x2 with 4 nodes)  
2. bring down one of the slave node. 
3. wait for some time and check the status. 

Actual results: all the bricks of a node shows faulty in status if slave node
to which atleast one of the brick connected goes down.


Expected results: the only brick which is connected the died node, should be
faulty.

--- Additional comment from Anand Avati on 2015-04-16 07:20:48 EDT ---

REVIEW: http://review.gluster.org/10121 (geo-rep: Status Enhancements) posted
(#3) for review on master by Aravinda VK (avishwan at redhat.com)

--- Additional comment from Anand Avati on 2015-04-17 02:19:39 EDT ---

REVIEW: http://review.gluster.org/10121 (geo-rep: Status Enhancements) posted
(#4) for review on master by Saravanakumar Arumugam (sarumuga at redhat.com)

--- Additional comment from Anand Avati on 2015-04-27 09:17:58 EDT ---

REVIEW: http://review.gluster.org/10121 (geo-rep: Status Enhancements) posted
(#5) for review on master by Aravinda VK (avishwan at redhat.com)

--- Additional comment from Anand Avati on 2015-04-28 04:21:43 EDT ---

REVIEW: http://review.gluster.org/10121 (geo-rep: Status Enhancements) posted
(#6) for review on master by Aravinda VK (avishwan at redhat.com)

--- Additional comment from Anand Avati on 2015-04-30 03:04:28 EDT ---

REVIEW: http://review.gluster.org/10121 (geo-rep: Status Enhancements) posted
(#7) for review on master by Aravinda VK (avishwan at redhat.com)

--- Additional comment from Anand Avati on 2015-05-02 07:59:55 EDT ---

REVIEW: http://review.gluster.org/10121 (geo-rep: Status Enhancements) posted
(#8) for review on master by Aravinda VK (avishwan at redhat.com)

--- Additional comment from Anand Avati on 2015-05-04 03:09:53 EDT ---

REVIEW: http://review.gluster.org/10121 (geo-rep: Status Enhancements) posted
(#9) for review on master by Aravinda VK (avishwan at redhat.com)


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1064309
[Bug 1064309] dist-geo-rep : all the bricks of a node shows faulty in
status if slave node to which atleast one of the brick connected goes down.
https://bugzilla.redhat.com/show_bug.cgi?id=1212410
[Bug 1212410] dist-geo-rep : all the bricks of a node shows faulty in
status if slave node to which atleast one of the brick connected goes down.
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list