[
https://issues.apache.org/jira/browse/HDFS-16510?focusedWorklogId=755078&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-755078
]
ASF GitHub Bot logged work on HDFS-16510:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Apr/22 03:46
Start Date: 11/Apr/22 03:46
Worklog Time Spent: 10m
Work Description: cndaimin commented on PR #4078:
URL: https://github.com/apache/hadoop/pull/4078#issuecomment-1094513479
@Jing9 @jojochuang @sodonnel @ayushtkn Do you have time to take a look on
this? I think it's a problem we need to fix in EC, thanks a lot.
Issue Time Tracking
-------------------
Worklog Id: (was: 755078)
Time Spent: 1h 20m (was: 1h 10m)
> Fix EC decommission when rack is not enough
> -------------------------------------------
>
> Key: HDFS-16510
> URL: https://issues.apache.org/jira/browse/HDFS-16510
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: block placement, ec
> Affects Versions: 3.3.1, 3.3.2
> Reporter: daimin
> Assignee: daimin
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
