Bug 1375849

Summary: [RFE] enable sharding with virt profile - /var/lib/glusterd/groups/virt
Product: [Community] GlusterFS Reporter: SATHEESARAN <sasundar>
Component: glusterdAssignee: bugs <bugs>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.8CC: amukherj, bugs, kdhananj
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: glusterfs-3.8.8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1375431 Environment:
Last Closed: 2017-01-16 12:26:06 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:
Bug Depends On: 1375431, 1376464, 1402215, 1402216    
Bug Blocks:    

Description SATHEESARAN 2016-09-14 05:30:19 UTC 
+++ This bug was initially created as a clone of Bug #1375431 +++

Description of problem:
-----------------------
Sharding seems to be most vital for the virt store usecase and this needs to be turned when the volume is optimized for virt-store

The following options needs to be added to the virt profile - /var/lib/glusterd/groups/virt

features.shard=on
cluster.data-self-heal-algorithm=full

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

How reproducible:
-----------------
Not applicable as this is a RFE

Steps to Reproduce:
-------------------
Not applicable as this is a RFE

Actual results:
---------------
sharding is not enabled by default by optimizing the volume for virt store

Expected results:
-----------------
Sharding should be enabled by default on optimizing the gluster volume for virt store usecase
Comment 1 Worker Ant 2016-12-13 15:29:02 UTC 
REVIEW: http://review.gluster.org/16120 (extras: Include shard and full-data-heal in virt group) posted (#1) for review on release-3.8 by Krutika Dhananjay (kdhananj)
Comment 2 Worker Ant 2016-12-15 15:49:48 UTC 
COMMIT: http://review.gluster.org/16120 committed in release-3.8 by Pranith Kumar Karampuri (pkarampu) 
------
commit d0d7a618fab67f3b0a6ad3f15d5fecc784341a0f
Author: Krutika Dhananjay <kdhananj>
Date:   Thu Dec 1 17:28:40 2016 +0530

    extras: Include shard and full-data-heal in virt group
    
            Backport of: http://review.gluster.org/15995
    
    Change-Id: Ibcfe069e2cc10cc1913ba5c9ca724b7dd3f8b147
    BUG: 1375849
    Signed-off-by: Krutika Dhananjay <kdhananj>
    Reviewed-on: http://review.gluster.org/16120
    Smoke: Gluster Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.org>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
Comment 3 Worker Ant 2016-12-21 23:22:11 UTC 
REVIEW: http://review.gluster.org/16259 (extras: Include shard and full-data-heal in virt group) posted (#1) for review on release-3.8-fb by Kevin Vigor (kvigor)
Comment 4 Niels de Vos 2017-01-16 12:26:06 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.8.8, please open a new bug report.

glusterfs-3.8.8 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://lists.gluster.org/pipermail/announce/2017-January/000064.html
[2] https://www.gluster.org/pipermail/gluster-users/