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

Daryn Sharp updated YARN-355:
-----------------------------

    Attachment: YARN-355.patch

Things got shuffled on main and caused dependency woes.

Removed private renew/cancel from YarnClientImpl that essentially was commented 
as it shouldn't be there.  Moved renewer into identifier class like other 
tokens.  Added much better tests.  Otherwise it's pretty much the same as the 
original patch.
                
> RM app submission jams under load
> ---------------------------------
>
>                 Key: YARN-355
>                 URL: https://issues.apache.org/jira/browse/YARN-355
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 3.0.0, 2.0.0-alpha, 0.23.6
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>         Attachments: YARN-355.branch-23.patch, YARN-355.patch
>
>
> The RM performs a loopback connection to itself to renew its own tokens.  If 
> app submissions consume all RPC handlers for {{ClientRMProtocol}}, then app 
> submissions block because it cannot loopback to itself to do the renewal.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to