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

ASF GitHub Bot commented on HDFS-17306:
---------------------------------------

LiuGuH opened a new pull request, #6385:
URL: https://github.com/apache/hadoop/pull/6385

   
   <!--
     Thanks for sending a pull request!
       1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
       2. Make sure your PR title starts with JIRA issue id, e.g., 
'HADOOP-17799. Your PR title ...'.
   -->
   
   ### Description of PR
   If a cluster has 3 nameservices: ns1, ns2,ns3, and  ns1 has observer nodes, 
and client  comminutes with nameservices via DFSRouter.
   
   If DFS_ROUTER_OBSERVER_READ_DEFAULT_KEY enable,  the client will receive all 
nameservices in RpcResponseHeaderProto.  And ns2,ns3 statidid is 
Long.MIN_VALUE,that is not necessary.
   
   We should reduce rpc response size if nameservices don't enable observer 
nodes.
   




> RBF:Router should not return nameservices that does not enable observer nodes 
> in RpcResponseHeaderProto
> -------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-17306
>                 URL: https://issues.apache.org/jira/browse/HDFS-17306
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: liuguanghua
>            Priority: Major
>
>       If a cluster has 3 nameservices: ns1, ns2,ns3, and  ns1 has observer 
> nodes, and client via DFSRouter comminutes with nns.
>       If DFS_ROUTER_OBSERVER_READ_DEFAULT_KEY enable,  the client will 
> receive all nameservices in RpcResponseHeaderProto. 
>        We should reduce rpc response size if nameservices don't enable 
> observer nodes.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to