[ 
https://issues.apache.org/jira/browse/HDFS-16613?focusedWorklogId=782197&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-782197
 ]

ASF GitHub Bot logged work on HDFS-16613:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 17/Jun/22 01:02
            Start Date: 17/Jun/22 01:02
    Worklog Time Spent: 10m 
      Work Description: hi-adachi commented on PR #4398:
URL: https://github.com/apache/hadoop/pull/4398#issuecomment-1158359483

   @lfxy The PR was merged, this is just FYI, the contribution guide says as 
follows. Thank you for your contribution.
   
   > https://cwiki.apache.org/confluence/display/hadoop/how+to+contribute
   > Once a "+1" comment is received from the automated patch testing system 
and a code reviewer has set the Reviewed flag on the issue's Jira, a committer 
should then evaluate it within a few days and either: commit it; or reject it 
with an explanation.  
   > 
   > Please be patient. Committers are busy people too. If no one responds to 
your patch after a few days, please make friendly reminders. Please incorporate 
other's suggestions into your patch if you think they're reasonable. Finally, 
remember that even a patch that is not committed is useful to the community.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 782197)
    Time Spent: 2h 10m  (was: 2h)

> EC: Improve performance of decommissioning dn with many ec blocks
> -----------------------------------------------------------------
>
>                 Key: HDFS-16613
>                 URL: https://issues.apache.org/jira/browse/HDFS-16613
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: ec, erasure-coding, namenode
>    Affects Versions: 3.4.0
>            Reporter: caozhiqiang
>            Assignee: caozhiqiang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>         Attachments: image-2022-06-07-11-46-42-389.png, 
> image-2022-06-07-17-42-16-075.png, image-2022-06-07-17-45-45-316.png, 
> image-2022-06-07-17-51-04-876.png, image-2022-06-07-17-55-40-203.png, 
> image-2022-06-08-11-38-29-664.png, image-2022-06-08-11-41-11-127.png
>
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> In a hdfs cluster with a lot of EC blocks, decommission a dn is very slow. 
> The reason is unlike replication blocks can be replicated from any dn which 
> has the same block replication, the ec block have to be replicated from the 
> decommissioning dn.
> The configurations dfs.namenode.replication.max-streams and 
> dfs.namenode.replication.max-streams-hard-limit will limit the replication 
> speed, but increase these configurations will create risk to the whole 
> cluster's network. So it should add a new configuration to limit the 
> decommissioning dn, distinguished from the cluster wide max-streams limit.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to