Uploaded image for project: 'Oozie'
  1. Oozie
  2. OOZIE-1993

Rerun fails during join in certain condition

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

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • trunk, 4.1.0
    • 4.2.0
    • core
    • None

    Description

      As Purshotam Shah described in this comment in OOZIE-1989:

      At first run job first fails at pig action. When we rerun from failed node, oozie.wf.rerun.failnodes=true. Oozie tries to join it and fails with error message.

      We should investigate why this is happening and fix it.

      Attachments

        1. worflow.xml
          9 kB
          Robert Kanter
        2. oozie-log.txt
          9 kB
          Robert Kanter
        3. OOZIE-1993-v3.patch
          27 kB
          Shwetha GS
        4. OOZIE-1993-v2.patch
          22 kB
          Shwetha GS
        5. OOZIE-1993.patch
          23 kB
          Shwetha GS

        Issue Links

        is broken by

        Bug - A problem which impairs or prevents the functions of the product. OOZIE-1879 Workflow Rerun causes error depending on the order of forked nodes

        • Blocker - Blocks development and/or testing work, production could not run
        • Closed
        relates to

        Bug - A problem which impairs or prevents the functions of the product. OOZIE-1989 NPE during a rerun with forks

        • Blocker - Blocks development and/or testing work, production could not run
        • Closed
        links to

        Web Link https://reviews.apache.org/r/33624/

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

          People

            shwethags Shwetha GS
            rkanter Robert Kanter
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment