Description of problem:
remove brick and also node from hadoop enabled volume/cluster.
we don't have script or steps documented for the above case.
What setup/configuration needs to be done ?( for removing it from cluster as well as changed needs to be done in Ambari setup)
This is a doc issue as we have no plans to automate the steps needed to scale down a storage pool. Note that you need to remove storage nodes in multiples of the replica count, which is always 2 for RHS.
Here are the manual steps to remove 2 servers from an existing pool:
(Assume the volume is HadoopVol, the servers to be removed are old-node1 and old-node2, and the brick is named /mnt/brick2)
1) run the gluster cli from any of the storage nodes:
gluster volume remove-brick HadoopVol old-node1:/mnt/brick2 \
NOTE: the data on these 2 servers in not accessible via gluster and a re-
balancing of data is likely required.
2) run the gluster cli on an existing storage node to detach the two old nodes:
gluster peer detach old-node1
gluster peer detach old-node2
3) rebalance the volume using the gluster cli on one of the storage nodes:
gluster volume rebalance HadoopVol start
The progress of the rebalancing can be seen via:
gluster volume rebalance HadoopVol status
4) remove the old nodes from Ambari:
go to the "HOSTS" tab in Ambari and select "remove host"
I have added these instructions to the internal installation guide. They will be moved to the Administrative guide by the time we release.
4) 4) remove the old nodes from Ambari:
go to the "HOSTS" tab in Ambari and select "Host Actions" on the right hand side. A dropdown will appear. Select "Delete Host"
Please modify point 4) as Erin suggested. I would also recommend to add to his text like "click on host you would like to delete" just before "and select Host Actions" because there is actually no 'Host Actions' button in Hosts tab, it appears after clicking on any hostname.
Please provide me a link to document, where was change done - we are working with few doc. versions on different sites (mojo, docbuilder, etc..). Is it point 4. in this one ? If yes, there were not added text proposed in comment #5 - description of action is not entirely correct right now in doc. I cant see log of changes on documentation-devel to verify this-
I assumed, that change was done in Administration Guide  located on documentation-devel. Scaling down section was updated like others and I suggested and it seems to be correct and verbose enough.
Documentation was updated, this issue is fixed -> VERIFIED
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.