[ 
https://issues.apache.org/jira/browse/HDFS-10391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194920#comment-16194920
 ] 

Kihwal Lee commented on HDFS-10391:
-----------------------------------

As Daryn explained, using service port may not be enough to allow health check 
to get through. May be the solution is to have datanodes talk to the regular 
rpc port and the health check and HA commands to the "service" port.   In my 
auto HA experimental setup, I didn't include the NN service port  in the 
datanode config for this specific reason.  In this setup, the health checks 
were minimally affected by regular rpc traffic and the HA commands were 
effectively skipping everyone in the regular call queue and only contending 
with the active handlers waiting on the lock.  There is a potential way to 
further prioritize such commands, but I don't think that's necessary if the 
number of handlers is not excessive.

I think having a separate port (rpc service) for health check and HA commands 
is a good idea, but it should also be separate from the datanode traffic.

> Always enable NameNode service RPC port
> ---------------------------------------
>
>                 Key: HDFS-10391
>                 URL: https://issues.apache.org/jira/browse/HDFS-10391
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode, namenode
>            Reporter: Arpit Agarwal
>            Assignee: Gergely Novák
>              Labels: Incompatible
>         Attachments: HDFS-10391.001.patch, HDFS-10391.002.patch, 
> HDFS-10391.003.patch, HDFS-10391.004.patch, HDFS-10391.005.patch, 
> HDFS-10391.006.patch, HDFS-10391.007.patch, HDFS-10391.008.patch, 
> HDFS-10391.009.patch, HDFS-10391.010.patch, HDFS-10391.v5-v6-delta.patch
>
>
> The NameNode should always be setup with a service RPC port so that it does 
> not have to be explicitly enabled by an administrator.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to