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] [Updated] (YARN-1363) Get / Cancel / Renew delegation token api should be non blocking
Date Wed, 26 Feb 2014 18:10:25 GMT

     [ https://issues.apache.org/jira/browse/YARN-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Zhijie Shen updated YARN-1363:

    Attachment: YARN-1363.8.patch

Create a new patch, which changes the solution. Instead of making the RMStateStore operate
token asynchronously, I created a RMDelegationTokenSecretManagerAsync which receive the operation
events from ClientRMService, handle them one by one on a separate thread. It can the RPC call
unblocked as well as keeping the change modular, though the size of patch is not reduced.
Another important change in this patch is that instead of touching the hadoop common code
base, I created separate get/cancel/renew response for yarn project only.

> 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, YARN-1363.2.patch, YARN-1363.3.patch, YARN-1363.4.patch,
YARN-1363.5.patch, YARN-1363.6.patch, YARN-1363.7.patch, YARN-1363.8.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