[Bugs] [Bug 1315659] [Tier]: Following volume restart, tierd shows failure at status on some nodes

bugzilla at redhat.com bugzilla at redhat.com
Tue Mar 15 06:06:06 UTC 2016


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



--- Comment #5 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/13646 committed in master by Dan Lambright
(dlambrig at redhat.com) 
------
commit 4d37476f264bdb7e213f302840ac3238dc6d9791
Author: hari gowtham <hgowtham at redhat.com>
Date:   Tue Mar 8 16:38:34 2016 +0530

    TIER: stopping the tierd when the volume goes down

    If there are large number of files to be migrated
    and by this time if the volume goes down, then the tierd
    has to be stopped. But on a huge query file list it keeps
    checking for each file before stopping. If the volume comes
    up before the old tierd dies then due to the
    presence of old tierd new one won't be created. After
    the old one completes the task, it dies and the status
    ends up as failed.

    This patch will check if the status is still running and then let
    it continue its work. Else it will stop running the tierd.

    Change-Id: I6522a4e2919e84bf502b99b13873795b9274f3cd
    BUG: 1315659
    Signed-off-by: hari gowtham <hgowtham at redhat.com>
    Reviewed-on: http://review.gluster.org/13646
    Tested-by: Dan Lambright <dlambrig at redhat.com>
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig at redhat.com>

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.


More information about the Bugs mailing list