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

Coordinators that undergo change endtime but are doneMaterialization, not getting picked for StatusTransit

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: trunk, 4.0.0
    • Fix Version/s: 4.1.0
    • Component/s: coordinator
    • Labels:
      None

      Description

      The coordinator 'change' utility to say, change endtime of a coordinator, makes
      a terminal job Running again, but if all actions are materialized, sets
      doneMaterialization to true, and keeps pending to true. So far so good.

      However, the expectation is StatusTransitService will pick this job and make
      its state terminal, if actions are in terminal states. But if the actions have
      terminated before this service's lastCheckTime, such jobs are not picked up.
      This leaves the coordinator(and its parent bundle action) forever running.

      Note that coordinator actions are properly terminated. Its only the coord job
      that stays in limbo.

        Attachments

        1. OOZIE-1632-trunk.patch
          13 kB
          Mona Chitnis
        2. OOZIE-1632.patch
          13 kB
          Mona Chitnis

          Issue Links

            Activity

              People

              • Assignee:
                chitnis Mona Chitnis
                Reporter:
                chitnis Mona Chitnis
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: