[
https://issues.apache.org/jira/browse/HDFS-16519?focusedWorklogId=760563&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-760563
]
ASF GitHub Bot logged work on HDFS-16519:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 22/Apr/22 02:54
Start Date: 22/Apr/22 02:54
Worklog Time Spent: 10m
Work Description: tasanuma commented on PR #4101:
URL: https://github.com/apache/hadoop/pull/4101#issuecomment-1105951309
Thanks for submitting this PR, @cndaimin. Thanks for your comment, @tomscut.
It seems a simple and nice feature. Our company is also concerned about the
network traffic of EC reconstructions when many datanodes get down. And I think
it is safe if it's disabled by default.
- Have you tried this feature with your cluster?
- What do you think about the relationship with the other similar
configurations, `dfs.datanode.data.transfer.bandwidthPerSec`,
`dfs.datanode.data.write.bandwidthPerSec`,
`dfs.datanode.ec.reconstruction.xmits.weight` ? Just for my curiosity, do you
have best practices regarding these settings?
Issue Time Tracking
-------------------
Worklog Id: (was: 760563)
Time Spent: 1h 20m (was: 1h 10m)
> Add throttler to EC reconstruction
> ----------------------------------
>
> Key: HDFS-16519
> URL: https://issues.apache.org/jira/browse/HDFS-16519
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode, ec
> Affects Versions: 3.3.1, 3.3.2
> Reporter: daimin
> Assignee: daimin
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> HDFS already have throttlers for data transfer(replication) and balancer, the
> throttlers reduce the impact of these background procedures to user
> read/write.
> We should add a throttler to EC background reconstruction too.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
