[
https://issues.apache.org/jira/browse/HDFS-13687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516754#comment-16516754
]
Chao Sun commented on HDFS-13687:
---------------------------------
Thanks [~xkrogen] and [~shv] for the very valuable comments! Regarding
Konstantin's comments:
1. Very good point. Sorry I didn't know that {{getServiceStatus}} requires
super privilege. Another option might be to add another interface/protocol to
get the active/standby state from NN, [as proposed in the original
JIRA|https://issues.apache.org/jira/browse/HDFS-2917?focusedCommentId=13204178&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13204178].
2. Yes good point. Perhaps we can reuse {{NameNodeHAProxyFactory}} to create
the factory needed in our case.
3. Can you elaborate more on this?. Currently
{{ConfiguredFailoverProxyProvider}} does assume all remote addresses are NN,
right?
Will go back to HDFS-12976 in the mean time.
> ConfiguredFailoverProxyProvider could direct requests to SBN
> ------------------------------------------------------------
>
> Key: HDFS-13687
> URL: https://issues.apache.org/jira/browse/HDFS-13687
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Chao Sun
> Assignee: Chao Sun
> Priority: Minor
> Attachments: HDFS-13687.000.patch
>
>
> In case there are multiple SBNs, and {{dfs.ha.allow.stale.reads}} is set to
> true, failover could go to a SBN which then may serve read requests from
> client. This may not be the expected behavior. This issue arises when we are
> working on HDFS-12943 and HDFS-12976.
> A better approach for this could be to check {{HAServiceState}} and find out
> the active NN when performing failover. This also can reduce the # of
> failovers the client has to do in case of multiple SBNs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
