[Bugs] [Bug 1428055] New: dht/rebalance: Increase maximum read block size from 128 KB to 1 MB

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1428055

            Bug ID: 1428055
           Summary: dht/rebalance: Increase maximum read block size from
                    128 KB to 1 MB
           Product: GlusterFS
           Version: mainline
         Component: core
          Assignee: bugs at gluster.org
          Reporter: vbellur at redhat.com
                CC: bugs at gluster.org



dht/rebalance: Increase maximum read block size from 128 KB to 1 MB

Summary:
- The maximum block size, `DHT_REBALANCE_BLKSIZE`, is set to 128 KB.
- As a result, migrating files in the megabytes to gigabytes can take much
longer than necessary.
- Some preliminary results by bumping the blocksize:

With 128 KB:
  [2016-08-04 11:40:19.251167] I [MSGID: 109028]
[dht-rebalance.c:2196:gf_defrag_status_get] 0-glusterfs: Rebalance is
completed. Time taken is 15.00 secs
  [2016-08-04 11:40:19.251189] I [MSGID: 109028]
[dht-rebalance.c:2200:gf_defrag_status_get] 0-glusterfs: Files migrated: 49,
size: 2569011200, lookups: 149, failures: 0, skipped: 0

With 1 MB:
  [2016-08-04 11:41:21.093662] I [MSGID: 109028]
[dht-rebalance.c:2196:gf_defrag_status_get] 0-glusterfs: Rebalance is
completed. Time taken is 7.00 secs
  [2016-08-04 11:41:21.093687] I [MSGID: 109028]
[dht-rebalance.c:2200:gf_defrag_status_get] 0-glusterfs: Files migrated: 49,
size: 2569011200, lookups: 149, failures: 0, skipped: 0

- This is a cherry-pick of D3670927 to 3.8.

Test Plan: Tested rebalance on devserver.

Reviewed By: dph, rwareing

Change-Id: Ide2edbf87ef9ae2b32a03f189c57b63e2f233fc8
Signed-off-by: Shreyas Siravara <sshreyas at fb.com>
Reviewed-on: http://review.gluster.org/16078
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
Smoke: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Kevin Vigor <kvigor at fb.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.