You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Boris Shkolnik (JIRA)" <ji...@apache.org> on 2010/05/25 01:18:24 UTC
[jira] Updated: (HADOOP-6638) try to relogin in a case of failed
RPC connection (expired tgt) only in case the subject is loginUser or
proxyUgi.realUser.
[ https://issues.apache.org/jira/browse/HADOOP-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-6638:
-----------------------------------
Attachment: HADOOP-6638.patch
> try to relogin in a case of failed RPC connection (expired tgt) only in case the subject is loginUser or proxyUgi.realUser.
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-6638
> URL: https://issues.apache.org/jira/browse/HADOOP-6638
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6638-BP20.patch, HADOOP-6638.patch
>
>
> when we get javax.security.sasl.SaslException in Client.setupSaslConnection() one possible problem could be an expired TGT.
> So we try to relogin from the keytab. But this should be attempted ONLY in case of loginUser or proxyUgi.realUser trying to connect.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.