[
https://issues.apache.org/jira/browse/HDFS-13522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17691247#comment-17691247
]
Takanobu Asanuma commented on HDFS-13522:
-----------------------------------------
[~simbadzina] Thanks again for implementing this feature.
I deployed RBF SBN with the latest trunk in my local environment and submitted
READ requests using several clients.
- Router and NameNodes: the latest trunk (including HDFS-13522 and HDFS-16767
and other bug fixes)
- clientA: the latest trunk (use ObserverReadProxyProvider)
- clientB: 3.3.4 (use ObserverReadProxyProvider)
- clientC: 2.7.x (which doesn't have ObserverReadProxyProvider)
As a result of that, only clientA was able to read from Observer. Router always
forwarded read requests from clientB and clientC to Acitve.
I looked into the design docs and discussions in this jira, and if I understand
correctly, the design intends that not only new clients but also old clients
can submit read requests to Observer. But it doesn't seem old clients can do it
now.
Am I missing some configuration to do that? Or is it still a work in progress?
> HDFS-13522: Add federated nameservices states to client protocol and
> propagate it between routers and clients.
> --------------------------------------------------------------------------------------------------------------
>
> 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
> Fix For: 3.4.0
>
> Attachments: HDFS-13522.001.patch, HDFS-13522.002.patch,
> HDFS-13522_WIP.patch, 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 50m
> 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 patch captures the state of all namespaces in the routers and propagates
> it to clients. A follow up patch will change router behavior to direct
> requests to the observer.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
