Bug 1012346 - Provide state of async tasks of all volumes in a new sub-command of 'volume status'
Summary: Provide state of async tasks of all volumes in a new sub-command of 'volume s...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: cli
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Krutika Dhananjay
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1016993
TreeView+ depends on / blocked
 
Reported: 2013-09-26 10:32 UTC by Krutika Dhananjay
Modified: 2014-04-17 11:48 UTC (History)
2 users (show)

Fixed In Version: glusterfs-3.5.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1016993 (view as bug list)
Environment:
Last Closed: 2014-04-17 11:48:51 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Krutika Dhananjay 2013-09-26 10:32:28 UTC
Description of problem:

The RHSC component needs a way of monitoring tasks using an inexpensive operation that can be consumed every 10 seconds to monitor all async tasks on all volumes in the cluster.

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

How reproducible:
N/A

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2013-09-26 11:00:48 UTC
REVIEW: http://review.gluster.org/6006 (cli,glusterd: Implement 'volume status tasks') posted (#1) for review on master by Krutika Dhananjay (kdhananj)

Comment 2 Anand Avati 2013-09-27 07:15:48 UTC
REVIEW: http://review.gluster.org/6006 (cli,glusterd: Implement 'volume status tasks') posted (#2) for review on master by Krutika Dhananjay (kdhananj)

Comment 3 Anand Avati 2013-09-27 07:16:20 UTC
REVIEW: http://review.gluster.org/6006 (cli,glusterd: Implement 'volume status tasks') posted (#3) for review on master by Krutika Dhananjay (kdhananj)

Comment 4 Anand Avati 2013-10-03 05:42:27 UTC
REVIEW: http://review.gluster.org/6006 (cli,glusterd: Implement 'volume status tasks') posted (#4) for review on master by Krutika Dhananjay (kdhananj)

Comment 5 Anand Avati 2013-10-07 06:28:46 UTC
REVIEW: http://review.gluster.org/6006 (cli,glusterd: Implement 'volume status tasks') posted (#5) for review on master by Krutika Dhananjay (kdhananj)

Comment 6 Anand Avati 2013-10-09 06:13:22 UTC
COMMIT: http://review.gluster.org/6006 committed in master by Anand Avati (avati) 
------
commit e51ca3c1c991416895e1e8693f7c3e6332d57464
Author: Krutika Dhananjay <kdhananj>
Date:   Tue Sep 24 17:01:46 2013 +0530

    cli,glusterd: Implement 'volume status tasks'
    
    oVirt's Gluster Integration needs an inexpensive command that can be
    executed every 10 seconds to monitor async tasks and their parameters,
    for all volumes.
    
    The solution involves adding a 'tasks' sub-command to 'volume status'
    to fetch only the async task IDs, type and other relevant parameters.
    Only the originator glusterd participates in this command as all the
    information needed is available on all the nodes. This is to make the
    command suitable for being executed every 10 seconds.
    
    Change-Id: I1edc607baf29b001a5585079dec681d7c641b3d1
    BUG: 1012346
    Signed-off-by: Krutika Dhananjay <kdhananj>
    Reviewed-on: http://review.gluster.org/6006
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Kaushal M <kaushal>

Comment 7 Niels de Vos 2014-04-17 11:48:51 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.5.0, please reopen this bug report.

glusterfs-3.5.0 has been announced on the Gluster Developers mailinglist [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/6137
[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.