[Bugs] [Bug 1264913] New: Data Tiering:Tiering deamon needs to be resilient when detach tier fails(tier vol should work as expected when detach tier fails)

[bugzilla at redhat.com]

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

            Bug ID: 1264913
           Summary: Data Tiering:Tiering deamon needs to be resilient when
                    detach tier fails(tier vol should work as expected
                    when detach tier fails)
           Product: GlusterFS
           Version: 3.7.4
         Component: tiering
          Assignee: bugs at gluster.org
          Reporter: nchilaka at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org



Description of problem:
=====================
When a detach tier fails, the state of the volume is stuck there itself.
That means any new file creates are going to cold tier instead of going to hot
tier.But as the detach failed, we must be doing writes to the hot tier and not
cold tier.
The user needs to issue a detach tier stop to route the IOs back to hot tier

[root at zod ~]# gluster v detach-tier uzbek start
volume detach-tier start: failed: Commit failed on yarrow. Please check log
file for details.
Tier command failed
[root at zod ~]# gluster v detach-tier uzbek status
                                    Node Rebalanced-files          size      
scanned      failures       skipped               status   run time in secs
                               ---------      -----------   -----------  
-----------   -----------   -----------         ------------     --------------
                               localhost                0        0Bytes        
    0             1             0               failed               0.00
[root at zod ~]# gluster v detach-tier uzbek status
                                    Node Rebalanced-files          size      
scanned      failures       skipped               status   run time in secs
                               ---------      -----------   -----------  
-----------   -----------   -----------         ------------     --------------
                               localhost                0        0Bytes        
    0             1             0               failed               0.00
[root at zod ~]# gluster v tier  uzbek status
Node                 Promoted files       Demoted files        Status           
---------            ---------            ---------            ---------        
localhost            0                    0                    failed           
volume rebalance: uzbek: success: 



Version-Release number of selected component (if applicable):
===========================================================
[root at zod uzbek]# 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
glglusterfs-debuginfo-3.7.4-0.33.git1d02d4b.el7.centos.x86_64
glusterfs-api-3.7.4-0.43.gitf139283.el7.centos.x86_64
ustglusterfs-client-xlators-3.7.4-0.43.gitf139283.el7.centos.x86_64
glusterfs-server-3.7.4-0.43.gitf139283.el7.centos.x86_64
erglusterfs-cli-3.7.4-0.43.gitf139283.el7.centos.x86_64
 glusterfs-libs-3.7.4-0.43.gitf139283.el7.centos.x86_64
-[root at zod uzbek]# 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.
[root at zod uzbek]# 



Steps to Reproduce:
-=====================
1.have a two node setup and create a tier volume with bricks spread across
nodes
2.Now have files in hot tier and issue a detach tier start from node@#1
3.immediatly, from node#2 kill the glusterd
4. It can be seen that the detach tier fails immediatly with "failed: Commit
failed on yarrow. Please check log file for details."

5. Now do new file creates from mount. It can be seen that the IOs are going to
cold tier. It must go to hot tier as the detach tier failed at beginning itselg

6. Also the user cant redo a detach tier start. He first needs to stop the
existing failed detach tier and then reissue

Actual results:


Expected results:


Additional info:

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