[ https://issues.apache.org/jira/browse/HDFS-14405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16822032#comment-16822032 ]
Íñigo Goiri commented on HDFS-14405: ------------------------------------ I think we should start with a unit test showing the issue. Probably two Routers and multiple threads getting and renewing tokens with 2 separately. > RBF: Client should be able to renew DT immediately after it fetched the DT > -------------------------------------------------------------------------- > > Key: HDFS-14405 > URL: https://issues.apache.org/jira/browse/HDFS-14405 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Fengnan Li > Assignee: Fengnan Li > Priority: Minor > > By the current design, once a dt is generated it needs to sync to other > routers as well as backing up in the state store, therefore there is a time > gap between other routers are able to know the existence of this token. > Ideally, the same client should be able to renew the token it just created > through fetchdt even though two calls are hitting two distinct routers. -- 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