[ https://issues.apache.org/jira/browse/HDFS-14035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16684433#comment-16684433 ]
Chen Liang commented on HDFS-14035: ----------------------------------- Thanks for the review [~shv]! The failed test TestConsistentReadsObserver is related. Turns out a side effect of using client protocol to discover server state is that the call to {{changeProxy}} could potentially updating client alignment context state id to most recent, if talked to active, introducing a race condition to {{testMsyncSimple}}. Post v0013 patch to resolve this. > NN status discovery does not leverage delegation token > ------------------------------------------------------ > > Key: HDFS-14035 > URL: https://issues.apache.org/jira/browse/HDFS-14035 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Chen Liang > Assignee: Chen Liang > Priority: Major > Attachments: HDFS-14035-HDFS-12943.001.patch, > HDFS-14035-HDFS-12943.002.patch, HDFS-14035-HDFS-12943.003.patch, > HDFS-14035-HDFS-12943.004.patch, HDFS-14035-HDFS-12943.005.patch, > HDFS-14035-HDFS-12943.006.patch, HDFS-14035-HDFS-12943.007.patch, > HDFS-14035-HDFS-12943.008.patch, HDFS-14035-HDFS-12943.009.patch, > HDFS-14035-HDFS-12943.010.patch, HDFS-14035-HDFS-12943.011.patch, > HDFS-14035-HDFS-12943.012.patch, HDFS-14035-HDFS-12943.013.patch > > > Currently ObserverReadProxyProvider uses > {{HAServiceProtocol#getServiceStatus}} to get the status of each NN. However > {{HAServiceProtocol}} does not leverage delegation token. So when running an > application on YARN and when YARN node manager makes this call > getServiceStatus, token authentication will fail, causing the application to > fail. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org