Bug 1169335 - gluster vol heal <VOLNAME> info takes long time to run even when there are no pending heals.
Summary: gluster vol heal <VOLNAME> info takes long time to run even when there are no...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ravishankar N
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-01 11:03 UTC by Ravishankar N
Modified: 2015-05-14 17:45 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.7.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-05-14 17:28:38 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Ravishankar N 2014-12-01 11:03:54 UTC
Description of problem:
'gluster v heal <VOLNAME> info` waits for about 10 seconds before printing the
 heal info and exiting.


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

How reproducible:
Always

Steps to Reproduce:
1. Create a 1x2 replica vol and start it.
2. Run 'gluster vol heal <VOLNAME> info'
3. It takes about 12 seconds before it prints anything.


Expected results:
With no pending heals, the command should return in a 2-3 seconds.

Comment 1 Anand Avati 2014-12-01 11:06:22 UTC
REVIEW: http://review.gluster.org/9224 (heal: free leaked frames.) posted (#1) for review on master by Ravishankar N (ravishankar)

Comment 2 Anand Avati 2014-12-02 01:38:00 UTC
REVIEW: http://review.gluster.org/9224 (heal: free leaked frames.) posted (#2) for review on master by Ravishankar N (ravishankar)

Comment 3 Anand Avati 2014-12-04 10:31:37 UTC
COMMIT: http://review.gluster.org/9224 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit 811abf66d158efa037f1314792f7c674a7640c50
Author: Ravishankar N <ravishankar>
Date:   Mon Dec 1 10:08:53 2014 +0000

    heal: free leaked frames.
    
    'gluster v heal <VOLNAME> info` waits for about 10 seconds before printing the
    heal info and exiting.
    
    Problem: glfsh_process_entries() is not freeing the frames it created.
    Thus when glfs_fini() is called, it busy waits for 10 seconds for background
    frames to finish before returning error.
    
    Fix: Destroy the frames in that are created in glfsh_process_entries().
    
    Change-Id: I5484d1b7301a355b913ae9c15b8a62471036c755
    BUG: 1169335
    Signed-off-by: Ravishankar N <ravishankar>
    Reviewed-on: http://review.gluster.org/9224
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Tested-by: Pranith Kumar Karampuri <pkarampu>

Comment 4 Niels de Vos 2015-05-14 17:28:38 UTC
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

Comment 5 Niels de Vos 2015-05-14 17:35:45 UTC
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

Comment 6 Niels de Vos 2015-05-14 17:38:07 UTC
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

Comment 7 Niels de Vos 2015-05-14 17:45:13 UTC
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


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