[Bugs] [Bug 1278385] New: Data Tiering:Detach tier operation should be resilient(continue) when the volume is restarted

[bugzilla at redhat.com]

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

            Bug ID: 1278385
           Summary: Data Tiering:Detach tier operation should be
                    resilient(continue) when the volume is restarted
           Product: Red Hat Gluster Storage
           Version: 3.1
         Component: glusterfs
     Sub Component: tiering
          Keywords: Triaged
          Severity: medium
          Priority: low
          Assignee: rhs-bugs at redhat.com
          Reporter: nchilaka at redhat.com
        QA Contact: nchilaka at redhat.com
                CC: bugs at gluster.org, dlambrig at redhat.com,
                    vagarwal at redhat.com
        Depends On: 1265184



+++ This bug was initially created as a clone of Bug #1265184 +++

Description of problem:
========================
I issued a detach tier start and while in progress or even when the detach tier
is completed, but not yet commited, I did a volume restart.
With this I expect the detach tier to continue, but I see that the detach tier
has stopped and says no detach tier is in progress.

The implications are as below:
1)the user will have to re-trigger the operation of detach tier start freshly
2)As the tier deamon is started instead of reblance demon(for detaching tier),
this can make promotes to hot tier and hence irritate the admin.


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

[root at zod glusterfs]# rpm -qa|grep gluster
glusterfs-3.7.4-0.43.gitf139283.el7.centos.x86_64
glusterfs-fuse-3.7.4-0.43.gitf139283.el7.centos.x86_64
glusterfs-debuginfo-3.7.4-0.33.git1d02d4b.el7.centos.x86_64
glusterfs-api-3.7.4-0.43.gitf139283.el7.centos.x86_64
glusterfs-client-xlators-3.7.4-0.43.gitf139283.el7.centos.x86_64
glusterfs-server-3.7.4-0.43.gitf139283.el7.centos.x86_64
glusterfs-cli-3.7.4-0.43.gitf139283.el7.centos.x86_64
gglusterfs-libs-3.7.4-0.43.gitf139283.el7.centos.x86_64
l[root at zod glusterfs]# gluster --version
glusterfs 3.7.4 built on Sep 19 2015 01:30:43
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU General
Public License.


How reproducible:
=================
easily


Steps to Reproduce(RHG3-9344):
=====================
 1)have a  "standard test volume configuration"
2)have with lot of data on hot tier
3)now issue a detach tier start on this volume
4)Now after some time, issue detach tier status and volume status too
5) now immediately stop the volume
6)check the detach tier status
7)Now restart the volume
8)check if the detach tier continues using detach tier status
9)after detach tier completes, issue a detach tier commit


Expected results:
================
detach tier must continue after a vol is restarted


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1265184
[Bug 1265184] Data Tiering:Detach tier operation should be
resilient(continue) when the volume is restarted
-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=6O7rF9vUqY&a=cc_unsubscribe