You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The decommission always fail when we start decommission multiple nodes on a cluster whose racks is not enough, a cluster with 6 racks to deploy RS-6-3, for example.
We find that those decommission nodes cover at least a rack, it's actulaly like we are decommission one or more racks. And rack decommission is not well supported currently, especially for cluster whose racks is not enough already.
In this patch, we add numOfExcludedRacks to indicate how many racks are in decommission(excluded) and fix the calculation of BlockPlacementStatusDefault#getAdditionalReplicasRequired. And in ErasureCodingWork#addTaskToDatanode, we adjust the process order as we should take care of decommission first, especially when rack is not enough.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The decommission always fail when we start decommission multiple nodes on a cluster whose racks is not enough, a cluster with 6 racks to deploy RS-6-3, for example.
We find that those decommission nodes cover at least a rack, it's actulaly like we are decommission one or more racks. And rack decommission is not well supported currently, especially for cluster whose racks is not enough already.
In this patch, we add
numOfExcludedRacks
to indicate how many racks are in decommission(excluded) and fix the calculation ofBlockPlacementStatusDefault#getAdditionalReplicasRequired
. And inErasureCodingWork#addTaskToDatanode
, we adjust the process order as we should take care of decommission first, especially when rack is not enough.