hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Íñigo Goiri (JIRA) <j...@apache.org>
Subject [jira] [Commented] (HDFS-14405) RBF: Client should be able to renew DT immediately after it fetched the DT
Date Fri, 19 Apr 2019 16:56:00 GMT

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

Íñigo Goiri commented on HDFS-14405:
------------------------------------

Thanks [~crh] for the clarification.
Doesn't the mini ZK cluster allow setting up this kind of situation with a 3rd node behind?

In any case, I guess the solution is to do a regular access and if there are failures to get
the token, then use a sync call.
Is this possible?

> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message