+++ 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) --- 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) --- 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) --- 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) --- 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) --- 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) --- 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)
REVIEW: http://review.gluster.org/10574 (geo-rep: Status Enhancements) posted (#1) for review on release-3.7 by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/10574 (geo-rep: Status Enhancements) posted (#2) for review on release-3.7 by Aravinda VK (avishwan)
COMMIT: http://review.gluster.org/10574 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit 6ebaa045ae8b2523e91c087cffae35cc4ec682c2 Author: Aravinda VK <avishwan> Date: Thu Mar 12 16:07:13 2015 +0530 geo-rep: Status Enhancements Discussion in gluster-devel http://www.gluster.org/pipermail/gluster-devel/2015-April/044301.html MASTER NODE - Master Volume Node MASTER VOL - Master Volume name MASTER BRICK - Master Volume Brick SLAVE USER - Slave User to which Geo-rep session is established SLAVE - <SLAVE_NODE>::<SLAVE_VOL> used in Geo-rep Create command SLAVE NODE - Slave Node to which Master worker is connected STATUS - Worker Status(Created, Initializing, Active, Passive, Faulty, Paused, Stopped) CRAWL STATUS - Crawl type(Hybrid Crawl, History Crawl, Changelog Crawl) LAST_SYNCED - Last Synced Time(Local Time in CLI output and UTC in XML output) ENTRY - Number of entry Operations pending.(Resets on worker restart) DATA - Number of Data operations pending(Resets on worker restart) META - Number of Meta operations pending(Resets on worker restart) FAILURES - Number of Failures CHECKPOINT TIME - Checkpoint set Time(Local Time in CLI output and UTC in XML output) CHECKPOINT COMPLETED - Yes/No or N/A CHECKPOINT COMPLETION TIME - Checkpoint Completed Time(Local Time in CLI output and UTC in XML output) XML output: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> cliOutput> geoRep> volume> name> sessions> session> session_slave> pair> master_node> master_brick> slave_user> slave/> slave_node> status> crawl_status> entry> data> meta> failures> checkpoint_completed> master_node_uuid> last_synced> checkpoint_time> checkpoint_completion_time> BUG: 1218586 Change-Id: I944a6c3c67f1e6d6baf9670b474233bec8f61ea3 Signed-off-by: Aravinda VK <avishwan> Reviewed-on: http://review.gluster.org/10121 Reviewed-by: Kotresh HR <khiremat> Reviewed-by: Vijay Bellur <vbellur> Reviewed-on: http://review.gluster.org/10574 Tested-by: Gluster Build System <jenkins.com>
REVIEW: http://review.gluster.org/10636 (geo-rep: Fix Default values in Xml output) posted (#1) for review on release-3.7 by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/10636 (geo-rep: Fix Default values in Xml output) posted (#2) for review on release-3.7 by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/10636 committed in release-3.7 by Vijay Bellur (vbellur) ------ commit 0b573c3d93159d4e801714211343b220c0f45e1e Author: Aravinda VK <avishwan> Date: Tue May 5 18:20:19 2015 +0530 geo-rep: Fix Default values in Xml output Default Values for last_synced, checkpoint_time and checkpoint_completion_time was zero instead of 'N/A' BUG: 1218586 Change-Id: I8a96688588dd6e22edf8bc06ee0f3afe12a9e0f5 Reviewed-on: http://review.gluster.org/10580 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/10636 Reviewed-by: Saravanakumar Arumugam <sarumuga> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.0, please open a new bug report. glusterfs-3.7.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user