[ 
https://issues.apache.org/jira/browse/HDFS-14660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887723#comment-16887723
 ] 

Ayush Saxena commented on HDFS-14660:
-------------------------------------

Thanx Chao!!!

bq. 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. 

I guess there is a specific behavior too, for when state ID isn't set i.e -1, 
The Observer serves the request without being bothered of the state. I am not 
sure if somebody had a use case for that. But to handle this scenario. This 
behavior would have to be changed. 

Well there is discussion at HDFS-14636, You may follow up there, with some 
proposals or some solution, Well I guess [~xkrogen] had some concerns there, 
Can conclude once he confirms. 

> [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
>
> 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

Reply via email to