Bug 1377185

Summary: Remove brick support for tiered volume
Product: [Community] GlusterFS Reporter: hari gowtham <hgowtham>
Component: tieringAssignee: hari gowtham <hgowtham>
Status: CLOSED WONTFIX QA Contact: bugs <bugs>
Severity: high Docs Contact:
Priority: high    
Version: mainlineCC: bugs
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-11-02 08:13:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description hari gowtham 2016-09-19 06:30:25 UTC 
Description of problem:
we dont support remove brick on 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:30:04 UTC 
Description of problem:
we dont support remove brick on tiered volume.

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


How reproducible:
100%

Steps to Reproduce:
1.create tiered volume of any configuration possible
2.try using remove brick command 
3.

Actual results:
wont be allowed on a tiered volume

Expected results:
remove brick should be allowed on tiered volume

Additional info:
add/remove brick commands are not supported on tiered volume.
The usualy add/ remove brick command wont work on tiered volume.
Use: gluster v tier volname remove-hot-brick hostname:brick
Comment 2 Amar Tumballi 2018-11-02 08:13:13 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.