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

Simbarashe Dzinamarira edited comment on HDFS-13522 at 7/25/22 11:58 PM:
-------------------------------------------------------------------------

[~zhengchenyu] I've scanned through your proposal.
 # When using RBF, clients do not need to know about all nameservices behind 
the routers. The NameserviceStateIdContextProto is a good idea (similar to the 
map in my proposal) but the information in it should originate in the router 
versus the client.
 # Maintaining the StateIdCache for each "client+callId" key builds up a lot of 
state in the router and a lot of it is very similar. In my proposal the keys 
for the extra map I add are the nameserviceIDs.
 # It is not clear to me how you handle the case in which a client switches 
between routers.

 


was (Author: simbadzina):
[~zhengchenyu] I've scanned through your proposal.
 # When using RBF, clients do not need to know about all nameservices behind 
the routers. The NameserviceStateIdContextProto is a good idea (similar to the 
map in my proposal) but the information in it should originate in the router 
versus the client.
 # Maintaining the StateIdCache for each "client+callId" key builds up a lot of 
state in the router and a lot of it is very similar. In my proposal the keys 
for the extra map I add are the nameserviceIDs.
 # It is not clear to me how you handle the case where a client switches 
between routers.

 

> RBF: Support observer node from Router-Based Federation
> -------------------------------------------------------
>
>                 Key: HDFS-13522
>                 URL: https://issues.apache.org/jira/browse/HDFS-13522
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: federation, namenode
>            Reporter: Erik Krogen
>            Assignee: Simbarashe Dzinamarira
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: HDFS-13522.001.patch, HDFS-13522.002.patch, 
> HDFS-13522_WIP.patch, HDFS-13522_proposal_zhengchenyu_v1.pdf, RBF_ Observer 
> support.pdf, Router+Observer RPC clogging.png, 
> ShortTerm-Routers+Observer.png, 
> observer_reads_in_rbf_proposal_simbadzina_v1.pdf, 
> observer_reads_in_rbf_proposal_simbadzina_v2.pdf
>
>          Time Spent: 20h
>  Remaining Estimate: 0h
>
> Changes will need to occur to the router to support the new observer node.
> One such change will be to make the router understand the observer state, 
> e.g. {{FederationNamenodeServiceState}}.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to