Bug 814074 - [64177411f7c032eeb2b65635a9ca4e5767a72b40]: gluster volume heal command timesout without any output
[64177411f7c032eeb2b65635a9ca4e5767a72b40]: gluster volume heal command times...
Product: GlusterFS
Classification: Community
Component: core (Show other bugs)
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Pranith Kumar K
Depends On:
Blocks: 817967
  Show dependency treegraph
Reported: 2012-04-19 03:44 EDT by Raghavendra Bhat
Modified: 2015-12-01 11:45 EST (History)
1 user (show)

See Also:
Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-24 13:36:45 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions: glusterfs-3.3.0qa40
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Raghavendra Bhat 2012-04-19 03:44:02 EDT
Description of problem:
Created a replicate volume with replica count 3. Mouted it via fuse and started untarring linux-kernel tarball. Immedietly brought 2 bricks down. After many entries were created (more than 4-5k), stopped untarring, brought the bricks up.
(volume start force) and gave volume heal command.

gluster volume heal command blocked for 2 minutes, then timedout and returned without any output (thus glusterd was not able to tell cli whether the heal operation was started or not, within 2 minutes.)

Version-Release number of selected component (if applicable):

How reproducible:


Steps to Reproduce:
1. Create a 3 replica volume start it and mount it.
2. Start untarring linux-kernel tarball and immedietly bring down 2 bricks
3. After around 4-5k entries have been created (number of entries that need heal can be known by gluster volume heal info command) stop untarring the tarball and bring the bricks up. (volume start force)
4. do gluster volume heal
Actual results:

gluster volume heal command blocks

Expected results:

gluster volume heal command should display whether the heal command that it sent to glusterd was successful or not

Additional info:
Comment 1 Anand Avati 2012-04-23 16:11:56 EDT
CHANGE: http://review.gluster.com/3194 (libglusterfs: Never block syncproc) merged in master by Anand Avati (avati@redhat.com)
Comment 2 Raghavendra Bhat 2012-05-09 05:31:20 EDT
Checked with glusterfs-3.3.0qa40 and gluster volume heal command did not block.
Comment 3 Raghavendra Bhat 2012-05-09 05:32:05 EDT
Checked with glusterfs-3.3.0qa40 and gluster volume heal command did not block.
Comment 4 Vijay Bellur 2012-08-21 01:54:23 EDT
CHANGE: http://review.gluster.org/3195 (syncop: Added scaling down logic) merged in master by Anand Avati (avati@redhat.com)

Note You need to log in before you can comment on or make changes to this bug.