[
https://issues.apache.org/jira/browse/HDFS-4780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669144#comment-13669144
]
Hudson commented on HDFS-4780:
------------------------------
Integrated in Hadoop-Yarn-trunk #224 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/224/])
HDFS-4780. Use the correct relogin method for services. Contributed by
Robert Parker. (Revision 1486974)
Result = SUCCESS
kihwal : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1486974
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/HftpFileSystem.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/GetImageServlet.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/SecondaryNameNode.java
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/ha/StandbyCheckpointer.java
> Use the correct relogin method for services
> -------------------------------------------
>
> Key: HDFS-4780
> URL: https://issues.apache.org/jira/browse/HDFS-4780
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: namenode
> Affects Versions: 3.0.0, 2.0.5-beta, 0.23.8
> Reporter: Kihwal Lee
> Assignee: Robert Parker
> Priority: Minor
> Fix For: 3.0.0, 2.0.5-beta
>
> Attachments: HDFS-4780-branch0.23v1.patch, HDFS-4780v1.patch
>
>
> A number of components call reloginFromKeytab() before making requests. For
> StandbyCheckpointer and SecondaryNameNode, where this can be called
> frequently, it generates many WARN messages like this:
> WARN security.UserGroupInformation: Not attempting to re-login since the last
> re-login was attempted less than 600 seconds before.
> Other than these messages, it doesn't do anything wrong. But it will be nice
> if it is changed to call checkTGTAndReloginFromKeytab() to avoid the
> potentially misleading WARN messages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
