hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1363) Get / Cancel / Renew delegation token api should be non blocking
Date Thu, 05 Dec 2013 21:45:37 GMT

    [ https://issues.apache.org/jira/browse/YARN-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840604#comment-13840604

Zhijie Shen commented on YARN-1363:

I've some different ideas about the implementation.

1. IMHO, we don't need to retain the synchronous behavior, like ClientRMService#submitApplication,
which involves writing RMStateStore as well. Or is there any point that I have missed?

2. In the RMStateStore, we can refer to the asynchronous process of app and attempt to deal
with token identifier. This should be much obvious.

3. The questionable and difficult part will be how users get notified of the success of getting/canceling/renewing
* RMDelegationTokenSecretManager need to maintain a list of ongoing operations, and listen
to the events from RMStateStore to get updated about their progress.
* It seems we need to modify the API like what YARN-1446 does. The client keeps querying until
it get the answer.
* The answer needs to be hold until the storing operation is finished.

Any idea?

> Get / Cancel / Renew delegation token api should be non blocking
> ----------------------------------------------------------------
>                 Key: YARN-1363
>                 URL: https://issues.apache.org/jira/browse/YARN-1363
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Omkar Vinit Joshi
>            Assignee: Zhijie Shen
>         Attachments: YARN-1363.1.patch
> Today GetDelgationToken, CancelDelegationToken and RenewDelegationToken are all blocking
> * As a part of these calls we try to update RMStateStore and that may slow it down.
> * Now as we have limited number of client request handlers we may fill up client handlers

This message was sent by Atlassian JIRA

View raw message