[
https://issues.apache.org/jira/browse/HDFS-14162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725556#comment-16725556
]
Konstantin Shvachko edited comment on HDFS-14162 at 12/20/18 3:27 AM:
----------------------------------------------------------------------
Attached a test, which captures this. It is similar to HDFS-14116, but Balancer
is a priority.
I see Balancer uses both Client and Namenode Protocols. So may be we should
create a combined proxy serving on both protocols. Why should there be
different proxies.
This is besides the fact that the ProxyFactory is the wrong one.
was (Author: shv):
Attached a test, which captures this. It is similar to HDFS-14116, but Balancer
is a priority.
I see Balancer uses both Client and Namenode Protocols. So may be we should
create a combined proxy serving on both protocols. Why should there be
different proxies.
This beside the fact that the ProxyFactory is a wrong one.
> Balancer should work with ObserverNode
> --------------------------------------
>
> Key: HDFS-14162
> URL: https://issues.apache.org/jira/browse/HDFS-14162
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Konstantin Shvachko
> Priority: Major
> Attachments: testBalancerWithObserver.patch
>
>
> Balancer provides a substantial RPC load on NameNode. It would be good to
> divert Balancer RPCs {{getBlocks()}}, etc. to ObserverNode. The main problem
> is that Balancer uses {{NamenodeProtocol}}, while ORPP currently supports
> only {{ClientProtocol}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
