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 "Kan Zhang (JIRA)" <ji...@apache.org> on 2011/01/06 23:40:45 UTC
[jira] Created: (HADOOP-7091) reloginFromKeytab() should happen
even if TGT can't be found
reloginFromKeytab() should happen even if TGT can't be found
------------------------------------------------------------
Key: HADOOP-7091
URL: https://issues.apache.org/jira/browse/HADOOP-7091
Project: Hadoop Common
Issue Type: Bug
Components: security
Reporter: Kan Zhang
Assignee: Kan Zhang
HADOOP-6965 introduced a getTGT() method and prevents reloginFromTGT() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed that, for example, JT will not be able to re-connect to NN after TGT expires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-7091) reloginFromKeytab() should happen
even if TGT can't be found
Posted by "Kan Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kan Zhang updated HADOOP-7091:
------------------------------
Description: HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires. (was: HADOOP-6965 introduced a getTGT() method and prevents reloginFromTGT() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed that, for example, JT will not be able to re-connect to NN after TGT expires.)
> reloginFromKeytab() should happen even if TGT can't be found
> ------------------------------------------------------------
>
> Key: HADOOP-7091
> URL: https://issues.apache.org/jira/browse/HADOOP-7091
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
>
> HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-7091) reloginFromKeytab() should happen
even if TGT can't be found
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980635#action_12980635 ]
Hudson commented on HADOOP-7091:
--------------------------------
Integrated in Hadoop-Common-22-branch #13 (See [https://hudson.apache.org/hudson/job/Hadoop-Common-22-branch/13/])
> reloginFromKeytab() should happen even if TGT can't be found
> ------------------------------------------------------------
>
> Key: HADOOP-7091
> URL: https://issues.apache.org/jira/browse/HADOOP-7091
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Fix For: 0.22.0
>
> Attachments: c7091-01.patch
>
>
> HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-7091) reloginFromKeytab() should happen
even if TGT can't be found
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978625#action_12978625 ]
Hadoop QA commented on HADOOP-7091:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12467683/c7091-01.patch
against trunk revision 1056006.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results: https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/162//testReport/
Findbugs warnings: https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/162//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/162//console
This message is automatically generated.
> reloginFromKeytab() should happen even if TGT can't be found
> ------------------------------------------------------------
>
> Key: HADOOP-7091
> URL: https://issues.apache.org/jira/browse/HADOOP-7091
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Attachments: c7091-01.patch
>
>
> HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-7091) reloginFromKeytab() should happen
even if TGT can't be found
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980240#action_12980240 ]
Todd Lipcon commented on HADOOP-7091:
-------------------------------------
Hi Kan, should this have gone in the 0.22 branch as well?
> reloginFromKeytab() should happen even if TGT can't be found
> ------------------------------------------------------------
>
> Key: HADOOP-7091
> URL: https://issues.apache.org/jira/browse/HADOOP-7091
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Fix For: 0.23.0
>
> Attachments: c7091-01.patch
>
>
> HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-7091) reloginFromKeytab() should happen
even if TGT can't be found
Posted by "Jakob Homan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jakob Homan updated HADOOP-7091:
--------------------------------
Resolution: Fixed
Fix Version/s: 0.23.0
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
I've committed this based on Todd's review. Resolving as fixed.
> reloginFromKeytab() should happen even if TGT can't be found
> ------------------------------------------------------------
>
> Key: HADOOP-7091
> URL: https://issues.apache.org/jira/browse/HADOOP-7091
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Fix For: 0.23.0
>
> Attachments: c7091-01.patch
>
>
> HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-7091) reloginFromKeytab() should happen
even if TGT can't be found
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978613#action_12978613 ]
Todd Lipcon commented on HADOOP-7091:
-------------------------------------
+1 pending test results.
> reloginFromKeytab() should happen even if TGT can't be found
> ------------------------------------------------------------
>
> Key: HADOOP-7091
> URL: https://issues.apache.org/jira/browse/HADOOP-7091
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Attachments: c7091-01.patch
>
>
> HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-7091) reloginFromKeytab() should happen
even if TGT can't be found
Posted by "Kan Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978932#action_12978932 ]
Kan Zhang commented on HADOOP-7091:
-----------------------------------
Todd, thanks for the review. Can't write unit tests for it, but we have verified the patch on clusters at Yahoo.
> reloginFromKeytab() should happen even if TGT can't be found
> ------------------------------------------------------------
>
> Key: HADOOP-7091
> URL: https://issues.apache.org/jira/browse/HADOOP-7091
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Attachments: c7091-01.patch
>
>
> HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-7091) reloginFromKeytab() should happen
even if TGT can't be found
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979925#action_12979925 ]
Hudson commented on HADOOP-7091:
--------------------------------
Integrated in Hadoop-Common-trunk-Commit #468 (See [https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/468/])
HADOOP-7091. reloginFromKeytab() should happen even if TGT can't be found. Contribued by Kan Zhang.
> reloginFromKeytab() should happen even if TGT can't be found
> ------------------------------------------------------------
>
> Key: HADOOP-7091
> URL: https://issues.apache.org/jira/browse/HADOOP-7091
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Fix For: 0.23.0
>
> Attachments: c7091-01.patch
>
>
> HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-7091) reloginFromKeytab() should happen
even if TGT can't be found
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12983567#action_12983567 ]
Hudson commented on HADOOP-7091:
--------------------------------
Integrated in Hadoop-Common-trunk-Commit #479 (See [https://hudson.apache.org/hudson/job/Hadoop-Common-trunk-Commit/479/])
> reloginFromKeytab() should happen even if TGT can't be found
> ------------------------------------------------------------
>
> Key: HADOOP-7091
> URL: https://issues.apache.org/jira/browse/HADOOP-7091
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Fix For: 0.22.0
>
> Attachments: c7091-01.patch
>
>
> HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-7091) reloginFromKeytab() should happen
even if TGT can't be found
Posted by "Kan Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kan Zhang updated HADOOP-7091:
------------------------------
Attachment: c7091-01.patch
Attaching a patch that allows reloginFromKeytab() to happen when getTGT() returns null. Also, making getTGT() a synchronized method.
> reloginFromKeytab() should happen even if TGT can't be found
> ------------------------------------------------------------
>
> Key: HADOOP-7091
> URL: https://issues.apache.org/jira/browse/HADOOP-7091
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Attachments: c7091-01.patch
>
>
> HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-7091) reloginFromKeytab() should happen
even if TGT can't be found
Posted by "Kan Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980245#action_12980245 ]
Kan Zhang commented on HADOOP-7091:
-----------------------------------
> Hi Kan, should this have gone in the 0.22 branch as well?
Yes. Can you help me get it committed? Thanks!
> reloginFromKeytab() should happen even if TGT can't be found
> ------------------------------------------------------------
>
> Key: HADOOP-7091
> URL: https://issues.apache.org/jira/browse/HADOOP-7091
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Fix For: 0.23.0
>
> Attachments: c7091-01.patch
>
>
> HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-7091) reloginFromKeytab() should happen
even if TGT can't be found
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980663#action_12980663 ]
Hudson commented on HADOOP-7091:
--------------------------------
Integrated in Hadoop-Common-trunk #574 (See [https://hudson.apache.org/hudson/job/Hadoop-Common-trunk/574/])
Moving HADOOP-7091 to 0.22 section in CHANGES.txt since it was put in branch
> reloginFromKeytab() should happen even if TGT can't be found
> ------------------------------------------------------------
>
> Key: HADOOP-7091
> URL: https://issues.apache.org/jira/browse/HADOOP-7091
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Fix For: 0.22.0
>
> Attachments: c7091-01.patch
>
>
> HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-7091) reloginFromKeytab() should happen
even if TGT can't be found
Posted by "Kan Zhang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kan Zhang updated HADOOP-7091:
------------------------------
Status: Patch Available (was: Open)
> reloginFromKeytab() should happen even if TGT can't be found
> ------------------------------------------------------------
>
> Key: HADOOP-7091
> URL: https://issues.apache.org/jira/browse/HADOOP-7091
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Attachments: c7091-01.patch
>
>
> HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-7091) reloginFromKeytab() should happen
even if TGT can't be found
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Lipcon updated HADOOP-7091:
--------------------------------
Fix Version/s: (was: 0.23.0)
0.22.0
Committed to 0.22 branch and moved it in CHANGES.txt
> reloginFromKeytab() should happen even if TGT can't be found
> ------------------------------------------------------------
>
> Key: HADOOP-7091
> URL: https://issues.apache.org/jira/browse/HADOOP-7091
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Fix For: 0.22.0
>
> Attachments: c7091-01.patch
>
>
> HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-7091) reloginFromKeytab() should happen
even if TGT can't be found
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980061#action_12980061 ]
Hudson commented on HADOOP-7091:
--------------------------------
Integrated in Hadoop-Common-trunk #573 (See [https://hudson.apache.org/hudson/job/Hadoop-Common-trunk/573/])
HADOOP-7091. reloginFromKeytab() should happen even if TGT can't be found. Contribued by Kan Zhang.
> reloginFromKeytab() should happen even if TGT can't be found
> ------------------------------------------------------------
>
> Key: HADOOP-7091
> URL: https://issues.apache.org/jira/browse/HADOOP-7091
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Fix For: 0.23.0
>
> Attachments: c7091-01.patch
>
>
> HADOOP-6965 introduced a getTGT() method and prevents reloginFromKeytab() from happening when TGT is not found. This results in the RPC layer not being able to refresh TGT after TGT expires. The reason is RPC layer only does relogin when the expired TGT is used and an exception is thrown. However, when that happens, the expired TGT will be removed from Subject. Therefore, getTGT() will return null and relogin will not be performed. We observed, for example, JT will not be able to re-connect to NN after TGT expires.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.