[
https://issues.apache.org/jira/browse/HDFS-14636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884281#comment-16884281
]
Ayush Saxena commented on HDFS-14636:
-------------------------------------
Hi [~xkrogen]
Isn't it unfair for the observer to serve the request to a client? When the
client doesn't intend to get it from the Observer, He didn't even set the state
id. The Observer should return it as a StandbyException. I know the present
behavior, when it isn't set, But I think we need to change a bit.
Moreover, This would be leading to inconsistencies too, Some time the request
would be from Active and Sometimes from Observer, and User may get different
responses.As per the proxy provider. He won't be expecting it too.
I tried checking HDFS-13923, I guess there too the intentions was to allow some
clients to go directly to active. But IMO for case by case for a client to
remove Observer nodes in the configs would be little tedious task.
Maybe handling this at ONN side can be tried. If there aren't any complications
around. :)
> SBN : If you configure the default proxy provider still read Request going to
> Observer namenode only.
> -----------------------------------------------------------------------------------------------------
>
> Key: HDFS-14636
> URL: https://issues.apache.org/jira/browse/HDFS-14636
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.1.1
> Reporter: Harshakiran Reddy
> Assignee: Ranith Sardar
> Priority: Major
> Labels: SBN
>
> {noformat}
> In Observer cluster, will configure the default proxy provider instead of
> "org.apache.hadoop.hdfs.server.namenode.ha.ObserverReadProxyProvider", still
> Read request going to Observer namenode only.{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
