Bug 1278279 - EC: File healing promotes it to hot tier
EC: File healing promotes it to hot tier
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: tier (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: RHGS 3.1.2
Assigned To: Pranith Kumar K
: ZStream
Depends On:
Blocks: 1260783 1260923 1282761 1283757
  Show dependency treegraph
Reported: 2015-11-05 02:23 EST by Bhaskarakiran
Modified: 2016-11-23 18:12 EST (History)
9 users (show)

See Also:
Fixed In Version: glusterfs-3.7.5-7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1282761 (view as bug list)
Last Closed: 2016-03-01 00:51:42 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0193 normal SHIPPED_LIVE Red Hat Gluster Storage 3.1 update 2 2016-03-01 05:20:36 EST

  None (edit)
Description Bhaskarakiran 2015-11-05 02:23:02 EST
Description of problem:

After the file is healed, its getting promoted to hot tier. While creating 1GB file on 8+4 ec volume, brought down 4 of the bricks and bricks are up after the file is created. File got healed on the 4 bricks and saw the file in the hot tier, which should not be.

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

[root@interstellar ~]# gluster --version
glusterfs 3.7.5 built on Oct 29 2015 10:11:53
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com>
You may redistribute copies of GlusterFS under the terms of the GNU General Public License.
[root@interstellar ~]# 

How reproducible:

Steps to Reproduce:
As in description

Actual results:
File getting promoted to hot tier after heal

Expected results:
Should remain in cold tier unless read/writes done to that file from client. Internal ops should not heat the file.

Additional info:
Comment 3 Joseph Elwin Fernandes 2015-11-13 03:46:00 EST
There are actually two issues here,

1) EC Selfheal traffic heats the file, as CTR Xlator is not distinguishing normal read-write FOP traffic from EC Sefheal FOP Traffic. Solution for this is detect the client-pid set in the FOP frame and ignore these FOPS in CTR Xlator. Need info from the EC dev Team, on the which client-pid EC Selfheal daemon uses to mark the FOPS different from regular FOPS.  

2) During a normal write the file gets heated up for read also, which is not correct and has performance cost w.r.t the extra updates to the database.  Well the reason for this is that each write that comes from the user to EC xlator converts to a read-modify-update FOPS. This read FOP doesnt have any marker on it to differentiate it from the regular read, and thus CTR tends to heat up the file.
Would require a marker on this read FOP or any such internal FOPs from EC xlator.
Comment 4 Bhaskarakiran 2015-11-26 04:17:05 EST
pls post the patch details.
Comment 6 Bhaskarakiran 2015-11-30 01:59:04 EST
verified this on 3.7.5-7 and works as expected.
Comment 8 errata-xmlrpc 2016-03-01 00:51:42 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.