[
https://issues.apache.org/jira/browse/HDFS-13522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16834021#comment-16834021
]
CR Hota commented on HDFS-13522:
--------------------------------
[~surendrasingh] Thanks for your comments.
For implementing a queue similar to FairCallQueue, Handlers have to understand
which downstream namenode a call is meant for and also whether its a
read/write. These aspects of a RPC can be inspected only once the call is
handled at the ClientProtocol implementation layer which callqueue won't have
any visibility into. Since we haven't yet finalized how to solve these, in the
interim we have taken a approach as shown in ShortTerm-Routers+Observer.png.
> 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: Chao Sun
> Priority: Major
> Attachments: HDFS-13522.001.patch, Router+Observer RPC clogging.png,
> ShortTerm-Routers+Observer.png
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
