Bug 1293659

Summary: Creation of files on hot tier volume taking very long time
Product: [Community] GlusterFS Reporter: Joseph Elwin Fernandes <josferna>
Component: tieringAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact: bugs <bugs>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.7.6CC: bugs, dlambrig, mpillai, nchilaka, rmekala, sankarshan
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-3.7.7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1293034 Environment:
Last Closed: 2016-04-19 07:51:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1282729, 1293034, 1319696, 1319698, 1377864    
Bug Blocks: 1260783    

Comment 1 Vijay Bellur 2015-12-22 15:43:00 UTC
REVIEW: http://review.gluster.org/13067 (ctr/sql: Providing for vol set for sqlcachesize and sqlWALsize and skip recording path) posted (#1) for review on release-3.7 by Joseph Fernandes

Comment 2 Vijay Bellur 2015-12-22 22:45:23 UTC
COMMIT: http://review.gluster.org/13067 committed in release-3.7 by Dan Lambright (dlambrig) 
------
commit a7de0cd095f799e3128f74fcccc57ac4d6fd0b6d
Author: Joseph Fernandes <josferna>
Date:   Tue Dec 15 18:29:06 2015 +0530

    ctr/sql: Providing for vol set for sqlcachesize and sqlWALsize and skip recording path
    
    1. Providing vol set option for cache size and wal autocheck point
       so that performance can be tuned.
    2. Removed recording of file path in the db. Trimming database columns.
       Path need not be stored in the db, as PARGFID, GFID, Basename is suffice
       to derive the path during migration.
    
    Backport of http://review.gluster.org/12972
    
    > Change-Id: I2cb590451a6d244bc91fe66c6dbffe2c2059dfb8
    > BUG: 1293034
    > Signed-off-by: Joseph Fernandes <josferna>
    > Reviewed-on: http://review.gluster.org/12972
    > Reviewed-by: N Balachandran <nbalacha>
    > Tested-by: Gluster Build System <jenkins.com>
    > Tested-by: NetBSD Build System <jenkins.org>
    > Reviewed-by: Dan Lambright <dlambrig>
    > Tested-by: Dan Lambright <dlambrig>
    Signed-off-by: Joseph Fernandes <josferna>
    
    Change-Id: Ia1c109983ec6ce75ed27b8c08f454f5b6283c31d
    BUG: 1293659
    Reviewed-on: http://review.gluster.org/13067
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Dan Lambright <dlambrig>
    Tested-by: Dan Lambright <dlambrig>

Comment 3 Kaushal 2016-04-19 07:51:49 UTC
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.7, please open a new bug report.

glusterfs-3.7.7 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user