Bug 763989 (GLUSTER-2257)

Summary:	enhance distribute to control the spread count (ie, control the hashing range)
Product:	[Community] GlusterFS	Reporter:	Amar Tumballi <amarts>
Component:	distribute	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	mainline	CC:	gluster-bugs, lakshmipathi, vraman
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	RTP	Mount Type:	---
Documentation:	DP	CRM:
Verified Versions:	master 39fee9a8f8264df61f77563acb048a441265afcf	Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Amar Tumballi 2010-12-29 10:14:10 UTC

Currently in distribute the range is same as number of subvolumes. We need a way to control this range, that way, we can control the range of hash per subvolume.

Comment 1 Amar Tumballi 2011-03-22 09:53:42 UTC

Need to have more discussion.. There will be some documentation required after the feature is implemented, and also we should come up with some tests to make sure this feature is working fine.

Moving this out of 3.2.0 as this is a feature and is not blocking anything required for 3.2.0 release.

Comment 2 Anand Avati 2011-07-14 05:01:43 UTC

PATCH: http://patches.gluster.com/patch/7710 in master (cluster/distribute: bring in directory-spread-count option)

Comment 3 Lakshmipathi G 2011-09-22 09:04:02 UTC

1)create a 4  brick dht volume ,mount it & create dir1.
2)check getfattr of dir1 on all backend
3)setfattr -n distribute.directory-spread-count -v 2  dir1
now range should be reduced to 2.
4)Create 1000 files on mount pt , these files should be distributed
to two bricks but not all four.