Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
Description
Sometimes we need to decomm a whole rack of nodes at the same time. When the decomm is in process; NN is slow.
The reason is when DecommissionManager checks the decomm status, it acquires namesystem's writer lock and iterates through all DNs; for each DN that is in decommissioning state, it check if replication is done for all the blocks on the machine via blockManager.isReplicationInProgress; for large cluster; the number of blocks on the machine could be big.
The fix could be to have DecommissionManager check for several decomm-in-progress nodes each time it aquires namesystem's writer lock.
Attachments
Attachments
Issue Links
- duplicates
-
HDFS-7411 Refactor and improve decommissioning logic into DecommissionManager
- Closed