hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3104) RM continues to send new AMRM tokens every heartbeat between rolling and activation
Date Wed, 28 Jan 2015 21:36:35 GMT

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

Jason Lowe updated YARN-3104:
    Attachment: YARN-3104.001.patch

As discussed in YARN-2314 the IPC layer makes it near impossible to close the connection,
and there's no support for re-negotiating the authentication of the connection.

This patch isn't a total fix, since it doesn't address the issue of re-authenticating the
connection using the new token.  However it does prevent the RM from constantly generating
tokens during the period between rolling and activating the next AMRM key and the corresponding
three lines of logging per application per second.

> RM continues to send new AMRM tokens every heartbeat between rolling and activation
> -----------------------------------------------------------------------------------
>                 Key: YARN-3104
>                 URL: https://issues.apache.org/jira/browse/YARN-3104
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.6.0
>            Reporter: Jason Lowe
>         Attachments: YARN-3104.001.patch
> When the RM rolls a new AMRM secret, it conveys this to the AMs when it notices they
are still connected with the old key.  However neither the RM nor the AM explicitly close
the connection or otherwise try to reconnect with the new secret.  Therefore the RM keeps
thinking the AM doesn't have the new token on every heartbeat and keeps sending new tokens
for the period between the key roll and the key activation.  Once activated the RM no longer
squawks in its logs about needing to generate a new token every heartbeat (i.e.: second) for
every app, but the apps can still be using the old token.  The token is only checked upon
connection to the RM.  The apps don't reconnect when sent a new token, and the RM doesn't
force them to reconnect by closing the connection.

This message was sent by Atlassian JIRA

View raw message