Bug 1377186 - rebalance support for tiered volume
Summary: rebalance support for tiered volume
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: GlusterFS
Classification: Community
Component: tiering
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: hari gowtham
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-19 06:32 UTC by hari gowtham
Modified: 2018-11-02 08:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-02 08:13:35 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description hari gowtham 2016-09-19 06:32:43 UTC
Description of problem:
we do not have a rebalance process for tiered volume

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 hari gowtham 2016-09-19 09:25:16 UTC
Description of problem:
we do not have a rebalance process for tiered volume

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1.create a tiered volume.
2.add a brick(still being worked on)
3.issue rebalance and check if rebalance actually takes place on tiered volume

Actual results:
there wasn't any rebalance command on tier.

Expected results:
rebalance should start

Additional info:
right from add/remove brick, the feature is not available on tiered volume.
This fix will be in after the add/remove brick support is made available on tiered volume.

Comment 2 Amar Tumballi 2018-11-02 08:13:35 UTC
Patch https://review.gluster.org/#/c/glusterfs/+/21331/ removes tier functionality from GlusterFS. 

https://bugzilla.redhat.com/show_bug.cgi?id=1642807 is used as the tracking bug for this. Recommendation is to convert your tier volume to regular volume (either replicate, ec, or plain distribute) with "tier detach" command before upgrade, and use backend features like dm-cache etc to utilize the caching from backend to provide better performance and functionality.


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