[
https://issues.apache.org/jira/browse/HDFS-13522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463444#comment-16463444
]
Chao Sun commented on HDFS-13522:
---------------------------------
Yes [~elgoiri] I agree that on {{RouterRpcClient}} side the implementation
should be like you said. The issue I'm trying to describe is that the
client-side config can enable/disable the observer reads, which should affect
the router-side behavior accordingly. For instance, if the client uses the
default {{ConfiguredFailoverProxyProvider}} for
{{dfs.client.failover.proxy.provider}}, then on the router side all read/write
requests should go through active NN. However, if client uses
{{StandbyReadProxyProvider}}, then read requests on the router side should go
to observer NN first.
> 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
> Priority: Major
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
