Bug 1201239 - DHT : disabling rebalance on specific files
Summary: DHT : disabling rebalance on specific files
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: mainline
Hardware: All
OS: All
low
low
Target Milestone: ---
Assignee: Jiffin
QA Contact:
URL:
Whiteboard: dht-rebalance-file
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-12 11:57 UTC by Jiffin
Modified: 2019-04-23 05:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-23 05:56:29 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Jiffin 2015-03-12 11:57:12 UTC 
Description of problem:

The rebalance will perform file migration for every regular files in a brick, if it is wrongly placed. Instead if there are brick specific file (should reside only on that brick), right now there is no method to distinguish those from the normal files.
Comment 1 Anand Avati 2015-03-12 12:01:29 UTC 
REVIEW: http://review.gluster.org/9865 (cluster/dht : disabling rebalance on specified files.) posted (#1) for review on master by jiffin tony Thottan (jthottan)
Comment 2 Anand Avati 2015-03-16 18:09:30 UTC 
REVIEW: http://review.gluster.org/9865 (cluster/dht : disabling rebalance on specified files.) posted (#2) for review on master by jiffin tony Thottan (jthottan)
Comment 3 Anand Avati 2015-03-17 11:36:19 UTC 
REVIEW: http://review.gluster.org/9865 (cluster/dht : disabling rebalance on specified files/folders.) posted (#3) for review on master by jiffin tony Thottan (jthottan)
Comment 4 Yaniv Kaul 2019-04-22 14:05:33 UTC 
None were merged. Status?
Comment 5 Jiffin 2019-04-23 05:56:29 UTC 
(In reply to Yaniv Kaul from comment #4)
> None were merged. Status?

The bug was opened in favour of trash translator in gluster, since there is not much active development for that translator, I am closing this bug as won't fix
Note You need to log in before you can comment on or make changes to this bug.