Bug 1265308 - Distribution cannot be prioritized when removing a brick
Summary: Distribution cannot be prioritized when removing a brick
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: GlusterFS
Classification: Community
Component: distribute
Version: mainline
Hardware: All
OS: Unspecified
medium
low
Target Milestone: ---
Assignee: Nithya Balachandran
QA Contact:
URL:
Whiteboard: dht-rebalance-usability
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-22 15:51 UTC by ashka
Modified: 2019-05-09 09:51 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-09 09:51:55 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description ashka 2015-09-22 15:51:52 UTC
Description of problem:
It is not possible to prioritize to which brick the files from the removed brick go. This could be useful in case of adding a new brick then removing an older brick in order to move all the files from the older brick to the new brick.

Comment 1 Soumya Koduri 2015-09-29 12:21:49 UTC
In my opinion, as files get distributed based on the elastic hashing algorithm used, it shall not be possible (by design) to move the files to a specific brick chose by admin. CCin few who shall be able to provide better inputs.

Comment 2 Kaleb KEITHLEY 2015-10-22 17:00:12 UTC
changing version to mainline in order to retire pre-release.

If you know the appropriate, correct version for this bug, please
set it.

Comment 3 Kaleb KEITHLEY 2015-10-22 17:06:51 UTC
changing version to mainline in order to retire pre-release.

If you know the appropriate, correct version for this bug, please
set it.

Comment 4 Kaleb KEITHLEY 2015-10-22 17:11:18 UTC
changing version to mainline in order to retire pre-release.

If you know the appropriate, correct version for this bug, please
set it.

Comment 5 Amar Tumballi 2019-05-09 09:51:55 UTC
We wouldn't be working on this feature in the near term, and hence will mark it as DEFERRED. We will revisit this after couple of more releases.


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