Bug 763989 (GLUSTER-2257) - enhance distribute to control the spread count (ie, control the hashing range)
Summary: enhance distribute to control the spread count (ie, control the hashing range)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-2257
Product: GlusterFS
Classification: Community
Component: distribute
Version: mainline
Hardware: All
OS: All
low
low
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-29 10:14 UTC by Amar Tumballi
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Regression: RTP
Mount Type: ---
Documentation: DP
CRM:
Verified Versions: master 39fee9a8f8264df61f77563acb048a441265afcf
Embargoed:


Attachments (Terms of Use)

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.


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