[
https://issues.apache.org/jira/browse/HADOOP-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12633149#action_12633149
]
Hairong Kuang commented on HADOOP-4116:
---------------------------------------
In the push model, if the proxy is allowed to transfer the block but the
destination does not allow to receive it. The whole/partial block will still be
transferred to the destination's system buffer but then be thrown away.
Although the block is not delivered to the target's datanode buffer, network
resources are still wasted.
Bo, I will create a patch to 0.18 the first thing when I get to the office
tomorrow.
> Balancer should provide better resource management
> --------------------------------------------------
>
> Key: HADOOP-4116
> URL: https://issues.apache.org/jira/browse/HADOOP-4116
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.17.0
> Reporter: Raghu Angadi
> Assignee: Hairong Kuang
> Priority: Blocker
> Fix For: 0.18.2, 0.19.0
>
> Attachments: balancerRM.patch
>
>
> The number of threads are currently limited on datanodes. Once these threads
> are occupied, DataNode does not accept any more requests (DOS). Recently we
> saw a case where most of the 256 threads were waiting in
> {{DataXceiver.replaceBlock()}} trying to acquire {{balancingSem}}. Since
> rebalancing is (heavily) throttled, I would think this would be the common
> case.
> These operations waiting for active rebalancing threads to finish need not
> take up a thread.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
