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 "Devaraj Das (JIRA)" <ji...@apache.org> on 2010/04/15 02:41:49 UTC
[jira] Updated: (HADOOP-6706) Relogin behavior for RPC clients
could be improved
[ https://issues.apache.org/jira/browse/HADOOP-6706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devaraj Das updated HADOOP-6706:
--------------------------------
Attachment: 6706.bp20.patch
Attaching a patch for the Y20 branch. "Exception" is caught and a relogin is attempted. We were debating whether to have relogin done outside the exception block before doing a saslConnect. But even in that case, we need to be able to handle exceptions since some other thread might be currently using the subject credentials that we are just about to destroy (in relogin) and that thread should retry the connection after a relogin. In any case the exception handling is required.
> Relogin behavior for RPC clients could be improved
> --------------------------------------------------
>
> Key: HADOOP-6706
> URL: https://issues.apache.org/jira/browse/HADOOP-6706
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.22.0
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Fix For: 0.22.0
>
> Attachments: 6706.bp20.patch
>
>
> Currently, the relogin in the RPC client happens on only a SaslException. But we have seen cases where other exceptions are thrown (like IllegalStateException when the client's ticket is invalid). This jira is to fix that behavior.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira