[
https://issues.apache.org/jira/browse/HADOOP-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833133#action_12833133
]
Owen O'Malley commented on HADOOP-6559:
---------------------------------------
I'd suggest instead making the relogin a non-static method on the UGI and have
it pass the Subject into the LoginContext. That will mean that it will keep the
same UGI and Subject and you can have the retry code inside of the doAs instead
of outside of it.
> The RPC client should try to re-login when it detects that the TGT expired
> --------------------------------------------------------------------------
>
> Key: HADOOP-6559
> URL: https://issues.apache.org/jira/browse/HADOOP-6559
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 0.22.0
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Fix For: 0.22.0
>
> Attachments: h-6559.1.patch, h-6559.2.patch, h-6559.3.patch
>
>
> Currently while making RPC calls, the client will throw an exception if the
> client is not able to use the TGT (expired or timedout). This could be
> improved - it could catch the exception and try doing a re-login.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
