[Bugs] [Bug 1208367] New: Data Tiering:Data moving to the tier(inertia) where data already exists instead of moving to hot tier first by default

[bugzilla at redhat.com]

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

            Bug ID: 1208367
           Summary: Data Tiering:Data moving to the tier(inertia) where
                    data already exists instead of moving to hot tier
                    first by default
           Product: GlusterFS
           Version: mainline
         Component: tiering
          Severity: urgent
          Assignee: bugs at gluster.org
          Reporter: nchilaka at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org



Description of problem:
=======================
adding new data to a tiered volume doesnt always get added to hot tier first by
default.
Suppose if it is an existing distribute volume with already data available on
it and after we convert the volume to a tiered volume by attaching tier, and
then add any data, the data still gets written to cold instead of hot tier,
hence making the hot tier useless.
In short, new data moves to the hot tier if the volume is a complete new tier
volume, else it moves to cold tier if it was already an existing regular volume
with data in it and got converted to tier vol.
Note: I haven't set any ctr options
Also, there is no volume quota policies set.
I had tested with bare minimum zero sized files,hence storage space should not
be an issue

Version-Release number of selected component (if applicable):
============================================================
Upstream nightly build
glusterfs 3.7dev built on Mar 31 2015 01:05:54
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:
==================
1.have a regular distribute volume and add data to it
2.Now attach a tier to convert this volume to tier volume
3. Now again add data to the tiered volume.
It can be observed that the new data is not getting written into new hot tier
but still getting added to the cold tier.


Expected results:
================
Any new data should get added to the hot tier

-- 
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.