[ https://issues.apache.org/jira/browse/HDFS-14660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16895473#comment-16895473 ]
Ayush Saxena commented on HDFS-14660: ------------------------------------- Sorry Didn't knew SBN Went till branch 2, Guess there are conflicts in cherry-picking the same patch to back branches, [~csun] Can you reopen and upload patch for the other branches? > [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 > Fix For: 3.3.0 > > Attachments: HDFS-14660.000.patch, HDFS-14660.001.patch, > HDFS-14660.002.patch, HDFS-14660.003.patch, HDFS-14660.004.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-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org