You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Chao Sun (JIRA)" <ji...@apache.org> on 2019/07/21 22:00:00 UTC
[jira] [Updated] (HDFS-14660) [SBN Read] ObserverNameNode should
throw StandbyException for requests not from ObserverProxyProvider
[ https://issues.apache.org/jira/browse/HDFS-14660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chao Sun updated HDFS-14660:
----------------------------
Attachment: HDFS-14660.000.patch
> [SBN Read] ObserverNameNode should throw StandbyException for requests not from ObserverProxyProvider
> -----------------------------------------------------------------------------------------------------
>
> Key: HDFS-14660
> URL: https://issues.apache.org/jira/browse/HDFS-14660
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Chao Sun
> Assignee: Chao Sun
> Priority: Major
> Attachments: HDFS-14660.000.patch
>
>
> In a HDFS HA cluster with consistent reads enabled (HDFS-12943), clients could be using either {{ObserverReadProxyProvider}}, {{ConfiguredProxyProvider}}, or something else. Since observer is just a special type of SBN and we allow transitions between them, a client NOT using {{ObserverReadProxyProvider}} will need to have {{dfs.ha.namenodes.<nameservice>}} include all NameNodes in the cluster, and therefore, it may send request to a observer node.
> For this case, we should check whether the {{stateId}} in the incoming RPC header is set or not, and throw an {{StandbyException}} when it is not.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org