Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1426496

Summary:	gdeploy config file should have the shard-block-size as 4MB and enable granular-entry-heal
Product:	[oVirt] cockpit-ovirt	Reporter:	SATHEESARAN <sasundar>
Component:	Gdeploy	Assignee:	Ramesh N <rnachimu>
Status:	CLOSED DUPLICATE	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	0.10.7-0.0.10	CC:	bugs
Target Milestone:	---	Flags:	sasundar: planning_ack? sasundar: devel_ack? sasundar: testing_ack?
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-24 11:33:10 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description SATHEESARAN 2017-02-24 03:21:45 UTC

Description of problem:
-----------------------
The shard-block-size is set to 512MB as per the latest generated gdeploy config file. The recommended shard size for the volumes is 4MB.

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
cockpit-ovirt-dashboard-0.10.7-0.0.11

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Start with the Gluster deployment
2. After gdeploy config file is generated, look for the shard-block-size on all the volumes

Actual results:
---------------
shard-block-size should be set to 512MB

Expected results:
-----------------
shard-block-size should be set to 512MB

Additional info:
----------------
With 4MB shards, granular-entry-heal provides faster healing times. So this feature too is required to be enabled for all the volumes ( both arbiter & replica 3 volume type )

So the effective volume options in the config file would look like below:

key=group,storage.owner-uid,storage.owner-gid,features.shard,features.shard-block-size,performance.low-prio-threads,cluster.data-self-heal-algorithm,cluster.locking-scheme,cluster.shd-wait-qlength,cluster.shd-max-threads,network.ping-timeout,user.cifs,performance.strict-o-direct,network.remote-dio,cluster.granular-entry-heal
value=virt,36,36,on,4MB,32,full,granular,10000,8,30,off,on,off,enable
brick_dirs=/gluster_bricks/vmstore/vmstore
ignore_volume_errors=no

Comment 1 SATHEESARAN 2017-02-24 03:24:16 UTC

(In reply to SATHEESARAN from comment #0)
> Description of problem:
> -----------------------
> The shard-block-size is set to 512MB as per the latest generated gdeploy
> config file. The recommended shard size for the volumes is 4MB.
> 
> 
> Expected results:
> -----------------
> shard-block-size should be set to 512MB
> 
>

Incorrect expected result as per comment0. Expectation is that shard-block-size should be set to 4MB

Comment 2 Ramesh N 2017-02-24 11:33:10 UTC

This bug is subset of changes suggested in other bz#1426527. So closing this as duplicate.

*** This bug has been marked as a duplicate of bug 1426527 ***