Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-9593

stack trace printed at ERROR for all yarn clients without hadoop.home set

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.0.0-alpha1
    • 2.1.0-beta
    • util
    • None

    Description

      This is the problem of HADOOP-9482 now showing up in a different application -one whose log4j settings haven't turned off all Shell logging.

      Unless you do that, all yarn clients will have a stack trace at error in their logs, which is generating false alarms and is utterly pointless. Why does this merit a stack trace? Why log it at error? It's not an error for a client app to not have these values set as long as they have the relevant JARs on their classpath. And if they don't, they'll get some classpath error instead

      Attachments

        1. HADOOP-9593-001.patch
          1 kB
          Steve Loughran
        2. HADOOP-9593-002.patch
          1 kB
          Steve Loughran

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            stevel@apache.org Steve Loughran
            stevel@apache.org Steve Loughran
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment