Hadoop Common
  1. Hadoop Common
  2. HADOOP-10015

UserGroupInformation prints out excessive ERROR warnings

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 3.0.0
    • Fix Version/s: 2.4.0
    • Component/s: security
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      In UserGroupInformation::doAs(), it prints out a log at ERROR level whenever it catches an exception.

      However, it prints benign warnings in the following paradigm:

       try {
              ugi.doAs(new PrivilegedExceptionAction<FileStatus>() {
                @Override
                public FileStatus run() throws Exception {
                  return fs.getFileStatus(nonExist);
                }
              });
            } catch (FileNotFoundException e) {
            }
      

      For example, FileSystem#exists() follows this paradigm. Distcp uses this paradigm too. The exception is expected therefore there should be no ERROR logs printed in the namenode logs.

      Currently, the user quickly finds out that the namenode log is quickly filled by benign ERROR logs when he or she runs distcp in secure set up. This behavior confuses the operators.

      This jira proposes to move the log to DEBUG level.

      1. HADOOP-10015.002.patch
        4 kB
        Haohui Mai
      2. HADOOP-10015.001.patch
        4 kB
        Haohui Mai
      3. HADOOP-10015.000.patch
        1 kB
        Haohui Mai
      4. 10015.v6.patch
        0.9 kB
        Nicolas Liochon
      5. 10015.v5.patch
        0.9 kB
        Nicolas Liochon
      6. 10015.v4.patch
        2 kB
        Nicolas Liochon
      7. 10015.v3.patch
        2 kB
        Nicolas Liochon

        Issue Links

          Activity

          Hide
          Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12606608/HADOOP-10015.000.patch
          against trunk revision .

          +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 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 javadoc. The javadoc tool did not generate any warning messages.

          +1 eclipse:eclipse. The patch built with eclipse:eclipse.

          +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 unit tests in hadoop-common-project/hadoop-common.

          +1 contrib tests. The patch passed contrib unit tests.

          Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3162//testReport/
          Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3162//console

          This message is automatically generated.

          Show
          Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12606608/HADOOP-10015.000.patch against trunk revision . +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 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . The javadoc tool did not generate any warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +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 unit tests in hadoop-common-project/hadoop-common. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3162//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3162//console This message is automatically generated.
          Hide
          Daryn Sharp added a comment -

          Would you please add an attachment with the stack trace? I don't believe you should see the issue described unless you are explicitly executing within a doAs and not catching exceptions. The logging was added back in the .20 days (by me) because it can be exceedingly hard to debug security issues. On a number of occasions, we had no idea kerberos/authentication/etc errors were occurring because something was gobbling the exceptions and/or going into a retry loop and appeared hung. Not logging IOExceptions effectively renders the logging useless because everything interesting (security related) is an IOException.

          Show
          Daryn Sharp added a comment - Would you please add an attachment with the stack trace? I don't believe you should see the issue described unless you are explicitly executing within a doAs and not catching exceptions. The logging was added back in the .20 days (by me) because it can be exceedingly hard to debug security issues. On a number of occasions, we had no idea kerberos/authentication/etc errors were occurring because something was gobbling the exceptions and/or going into a retry loop and appeared hung. Not logging IOExceptions effectively renders the logging useless because everything interesting (security related) is an IOException.
          Hide
          Haohui Mai added a comment -

          Hi Daryn Sharp,

          I should have explained it more clearly.

          During in-house testing, we (hortonworks) have observed a lot of these warnings when doing distcp in secure clusters. To further demonstrate the problem, I extract some basic logic in distcp into a unit test.

          The log is definitely useful, but let's put it into the DEBUG level so that it won't confuse the operators then.

          Show
          Haohui Mai added a comment - Hi Daryn Sharp , I should have explained it more clearly. During in-house testing, we (hortonworks) have observed a lot of these warnings when doing distcp in secure clusters. To further demonstrate the problem, I extract some basic logic in distcp into a unit test. The log is definitely useful, but let's put it into the DEBUG level so that it won't confuse the operators then.
          Hide
          Hadoop QA added a comment -

          +1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12606906/HADOOP-10015.001.patch
          against trunk revision .

          +1 @author. The patch does not contain any @author tags.

          +1 tests included. The patch appears to include 1 new or modified test files.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 javadoc. The javadoc tool did not generate any warning messages.

          +1 eclipse:eclipse. The patch built with eclipse:eclipse.

          +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 unit tests in hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs.

          +1 contrib tests. The patch passed contrib unit tests.

          Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3176//testReport/
          Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3176//console

          This message is automatically generated.

          Show
          Hadoop QA added a comment - +1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12606906/HADOOP-10015.001.patch against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . The javadoc tool did not generate any warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +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 unit tests in hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3176//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3176//console This message is automatically generated.
          Hide
          Hadoop QA added a comment -

          +1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12607265/HADOOP-10015.002.patch
          against trunk revision .

          +1 @author. The patch does not contain any @author tags.

          +1 tests included. The patch appears to include 1 new or modified test files.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 javadoc. The javadoc tool did not generate any warning messages.

          +1 eclipse:eclipse. The patch built with eclipse:eclipse.

          +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 unit tests in hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs.

          +1 contrib tests. The patch passed contrib unit tests.

          Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3191//testReport/
          Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3191//console

          This message is automatically generated.

          Show
          Hadoop QA added a comment - +1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12607265/HADOOP-10015.002.patch against trunk revision . +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 1 new or modified test files. +1 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . The javadoc tool did not generate any warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +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 unit tests in hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3191//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3191//console This message is automatically generated.
          Hide
          Daryn Sharp added a comment -

          I guess I'm surprised that distcp is operating within an explicit doAs. Logging doesn't occur when an exception generated under the login/current user, just an explicit doAs.

          I do agree that the logging can be annoying at times, but it's a lifesaver at other times. Like code that loops w/o logging the exception that triggered a retry, code that swallows an exception, code that catches and throws a generic "something failed" exception, etc.

          If it's a debug level, then the logging becomes worthless - it's not possible to retroactively enable debug logging to analyze race conditions or transient errors. Debug is too voluminous to enable for catching problems in production.

          Perhaps a middle of the road solution is to create a new logger instance for doas, named with a ".doAs" suffix to the ugi class. That way those that want to disable the logging may do so via log4j.properties.

          Show
          Daryn Sharp added a comment - I guess I'm surprised that distcp is operating within an explicit doAs. Logging doesn't occur when an exception generated under the login/current user, just an explicit doAs. I do agree that the logging can be annoying at times, but it's a lifesaver at other times. Like code that loops w/o logging the exception that triggered a retry, code that swallows an exception, code that catches and throws a generic "something failed" exception, etc. If it's a debug level, then the logging becomes worthless - it's not possible to retroactively enable debug logging to analyze race conditions or transient errors. Debug is too voluminous to enable for catching problems in production. Perhaps a middle of the road solution is to create a new logger instance for doas, named with a ".doAs" suffix to the ugi class. That way those that want to disable the logging may do so via log4j.properties.
          Hide
          Luke Lu added a comment -

          Would excluding common innocuous exceptions like FileNotFoundException from error logging (still log all exception at debug level) cover most cases here?

          Show
          Luke Lu added a comment - Would excluding common innocuous exceptions like FileNotFoundException from error logging (still log all exception at debug level) cover most cases here?
          Hide
          stack added a comment -

          I just committed HADOOP-10274 without reading this one. It sets log level to DEBUG. I just saw your comments above Daryn Sharp You want me to revert it?

          Show
          stack added a comment - I just committed HADOOP-10274 without reading this one. It sets log level to DEBUG. I just saw your comments above Daryn Sharp You want me to revert it?
          Hide
          stack added a comment -

          s/DEBUG/WARN/ in above.

          Haohui Mai suggested closing this as a DUPLICATE but sounds like you lads might want to do more than just set log level down to WARN so leaving as is for now till hear more.

          Show
          stack added a comment - s/DEBUG/WARN/ in above. Haohui Mai suggested closing this as a DUPLICATE but sounds like you lads might want to do more than just set log level down to WARN so leaving as is for now till hear more.
          Hide
          Nicolas Liochon added a comment -

          I came into this as well.

          v3 proposes:

          • to fix the typo
          • to log as info by default
          • to log as debug when the exception comes from a user interrupt
          Show
          Nicolas Liochon added a comment - I came into this as well. v3 proposes: to fix the typo to log as info by default to log as debug when the exception comes from a user interrupt
          Hide
          Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12634210/10015.v3.patch
          against trunk revision .

          +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 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 javadoc. There were no new javadoc warning messages.

          +1 eclipse:eclipse. The patch built with eclipse:eclipse.

          +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 failed these unit tests in hadoop-common-project/hadoop-common:

          org.apache.hadoop.metrics2.impl.TestMetricsSystemImpl

          +1 contrib tests. The patch passed contrib unit tests.

          Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3667//testReport/
          Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3667//console

          This message is automatically generated.

          Show
          Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12634210/10015.v3.patch against trunk revision . +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 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . There were no new javadoc warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +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 failed these unit tests in hadoop-common-project/hadoop-common: org.apache.hadoop.metrics2.impl.TestMetricsSystemImpl +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3667//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3667//console This message is automatically generated.
          Hide
          Nicolas Liochon added a comment -

          v4 is the result of an offline review with Devaraj Das: the info / log was inverted.

          Show
          Nicolas Liochon added a comment - v4 is the result of an offline review with Devaraj Das : the info / log was inverted.
          Hide
          Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12635562/10015.v4.patch
          against trunk revision .

          +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 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 javadoc. There were no new javadoc warning messages.

          +1 eclipse:eclipse. The patch built with eclipse:eclipse.

          +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 unit tests in hadoop-common-project/hadoop-common.

          +1 contrib tests. The patch passed contrib unit tests.

          Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3682//testReport/
          Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3682//console

          This message is automatically generated.

          Show
          Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12635562/10015.v4.patch against trunk revision . +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 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . There were no new javadoc warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +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 unit tests in hadoop-common-project/hadoop-common. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3682//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3682//console This message is automatically generated.
          Hide
          Daryn Sharp added a comment -

          I'll hesitantly reverse course and say just make it a debug. Much cleaner than a bunch of conditionals on exceptions.

          Show
          Daryn Sharp added a comment - I'll hesitantly reverse course and say just make it a debug. Much cleaner than a bunch of conditionals on exceptions.
          Hide
          Haohui Mai added a comment -

          Since the related fix has landed trunk a while ago, maybe it is better to file a separate jira to discuss further improvement?

          Show
          Haohui Mai added a comment - Since the related fix has landed trunk a while ago, maybe it is better to file a separate jira to discuss further improvement?
          Hide
          Nicolas Liochon added a comment -

          I'll hesitantly reverse course and say just make it a debug. Much cleaner than a bunch of conditionals on exceptions.

          I'm ok with that.

          Since the related fix has landed trunk a while ago, maybe it is better to file a separate jira to discuss further improvement?

          I hope that changing a an error/warn log to debug will not require too much discussion, but if you really want it I can create a new jira.

          Show
          Nicolas Liochon added a comment - I'll hesitantly reverse course and say just make it a debug. Much cleaner than a bunch of conditionals on exceptions. I'm ok with that. Since the related fix has landed trunk a while ago, maybe it is better to file a separate jira to discuss further improvement? I hope that changing a an error/warn log to debug will not require too much discussion, but if you really want it I can create a new jira.
          Hide
          stack added a comment -

          I'd be +1 on DEBUG (Opening a new issue to discuss what level a message should be logged at is OTT).

          Show
          stack added a comment - I'd be +1 on DEBUG (Opening a new issue to discuss what level a message should be logged at is OTT).
          Hide
          Nicolas Liochon added a comment -

          So here is the v5, hopefully with a limited regression risk

          Show
          Nicolas Liochon added a comment - So here is the v5, hopefully with a limited regression risk
          Hide
          Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12636029/10015.v5.patch
          against trunk revision .

          +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 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 javadoc. There were no new javadoc warning messages.

          +1 eclipse:eclipse. The patch built with eclipse:eclipse.

          +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 unit tests in hadoop-common-project/hadoop-common.

          +1 contrib tests. The patch passed contrib unit tests.

          Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3688//testReport/
          Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3688//console

          This message is automatically generated.

          Show
          Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12636029/10015.v5.patch against trunk revision . +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 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . There were no new javadoc warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +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 unit tests in hadoop-common-project/hadoop-common. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3688//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3688//console This message is automatically generated.
          Hide
          Suresh Srinivas added a comment -

          Comment:
          isDebugEnabled check is needed around the section that prints debug log.

          Show
          Suresh Srinivas added a comment - Comment: isDebugEnabled check is needed around the section that prints debug log.
          Hide
          Tsz Wo Nicholas Sze added a comment -

          Or we may simply remove the log message. It does not look useful. UserGroupInformation.doAs(..) is a public API. If the caller wants to see the exception message, they should print it when the exception is caught.

          Show
          Tsz Wo Nicholas Sze added a comment - Or we may simply remove the log message. It does not look useful. UserGroupInformation.doAs(..) is a public API. If the caller wants to see the exception message, they should print it when the exception is caught.
          Hide
          Nicolas Liochon added a comment -

          Thanks for the review, all.The v6 adds the isDebugEnabled check.

          Show
          Nicolas Liochon added a comment - Thanks for the review, all.The v6 adds the isDebugEnabled check.
          Hide
          Hadoop QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12636253/10015.v6.patch
          against trunk revision .

          +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 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 javadoc. There were no new javadoc warning messages.

          +1 eclipse:eclipse. The patch built with eclipse:eclipse.

          +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 unit tests in hadoop-common-project/hadoop-common.

          +1 contrib tests. The patch passed contrib unit tests.

          Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3696//testReport/
          Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3696//console

          This message is automatically generated.

          Show
          Hadoop QA added a comment - -1 overall . Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12636253/10015.v6.patch against trunk revision . +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 javac . The applied patch does not increase the total number of javac compiler warnings. +1 javadoc . There were no new javadoc warning messages. +1 eclipse:eclipse . The patch built with eclipse:eclipse. +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 unit tests in hadoop-common-project/hadoop-common. +1 contrib tests . The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/3696//testReport/ Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/3696//console This message is automatically generated.
          Hide
          Tsz Wo Nicholas Sze added a comment -

          +1 patch looks good.

          Show
          Tsz Wo Nicholas Sze added a comment - +1 patch looks good.
          Hide
          Tsz Wo Nicholas Sze added a comment -

          I have committed this. Thanks, Nicolas!

          Show
          Tsz Wo Nicholas Sze added a comment - I have committed this. Thanks, Nicolas!
          Hide
          Hudson added a comment -

          SUCCESS: Integrated in Hadoop-trunk-Commit #5388 (See https://builds.apache.org/job/Hadoop-trunk-Commit/5388/)
          HADOOP-10015. UserGroupInformation prints out excessive warnings. Contributed by Nicolas Liochon (szetszwo: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1580977)

          • /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
          • /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
          Show
          Hudson added a comment - SUCCESS: Integrated in Hadoop-trunk-Commit #5388 (See https://builds.apache.org/job/Hadoop-trunk-Commit/5388/ ) HADOOP-10015 . UserGroupInformation prints out excessive warnings. Contributed by Nicolas Liochon (szetszwo: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1580977 ) /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
          Hide
          Hudson added a comment -

          FAILURE: Integrated in Hadoop-Yarn-trunk #520 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/520/)
          HADOOP-10015. UserGroupInformation prints out excessive warnings. Contributed by Nicolas Liochon (szetszwo: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1580977)

          • /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
          • /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
          Show
          Hudson added a comment - FAILURE: Integrated in Hadoop-Yarn-trunk #520 (See https://builds.apache.org/job/Hadoop-Yarn-trunk/520/ ) HADOOP-10015 . UserGroupInformation prints out excessive warnings. Contributed by Nicolas Liochon (szetszwo: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1580977 ) /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
          Hide
          Hudson added a comment -

          FAILURE: Integrated in Hadoop-Mapreduce-trunk #1737 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1737/)
          HADOOP-10015. UserGroupInformation prints out excessive warnings. Contributed by Nicolas Liochon (szetszwo: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1580977)

          • /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
          • /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
          Show
          Hudson added a comment - FAILURE: Integrated in Hadoop-Mapreduce-trunk #1737 (See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1737/ ) HADOOP-10015 . UserGroupInformation prints out excessive warnings. Contributed by Nicolas Liochon (szetszwo: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1580977 ) /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
          Hide
          Hudson added a comment -

          FAILURE: Integrated in Hadoop-Hdfs-trunk #1712 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1712/)
          HADOOP-10015. UserGroupInformation prints out excessive warnings. Contributed by Nicolas Liochon (szetszwo: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1580977)

          • /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
          • /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
          Show
          Hudson added a comment - FAILURE: Integrated in Hadoop-Hdfs-trunk #1712 (See https://builds.apache.org/job/Hadoop-Hdfs-trunk/1712/ ) HADOOP-10015 . UserGroupInformation prints out excessive warnings. Contributed by Nicolas Liochon (szetszwo: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1580977 ) /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt /hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java

            People

            • Assignee:
              Nicolas Liochon
              Reporter:
              Haohui Mai
            • Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development