Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-1135

Workflow log4j appender expects DAG not to change

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.2.0
    • ambari-web
    • None

    Description

      Each job may contain DAG information, but the log4j appender ignores it for all but the first job in the workflow. This is a problem because Pig may generate multiple independent DAGs for a single script, e.g. if "exec" is called in the middle of the script. The log4j appender needs to merge together the DAG information for all the jobs in a workflow instead of assuming that the DAG won't change.

      Attachments

        Issue Links

        duplicates

        Bug - A problem which impairs or prevents the functions of the product. AMBARI-1167 App not showing graphs for all MR jobs run

        • Critical - Crashes, loss of data, severe memory leak.
        • Resolved

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

          People

            billie Billie Rinaldi
            billie Billie Rinaldi
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment