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

On startup, StatusTransitService can transition Coordinators that were in PRESUSPENDED to RUNNING

    XMLWordPrintableJSON

    Details

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

      Description

      You can reproduce this issue easily:

      1. Submit a coordinator job that starts in the future
        • It enters PREP state
      2. Suspend the coordinator job
        • It enters PREPSUSPENDED state
      3. Restart Oozie and wait about a minute or so
        • The job transitions back to RUNNING state by itself

      This is the wrong behavior for two reasons:

      1. PREPSUSPENDED --> RUNNING is not a valid transition (it has to go to PREP first)
      2. It shouldn't resume by itself

      The log shows that the StatusTransitService is doing it.

        Attachments

        1. OOZIE-2017.patch
          4 kB
          Robert Kanter
        2. OOZIE-2017.patch
          4 kB
          Robert Kanter
        3. OOZIE-2017.patch
          4 kB
          Robert Kanter

          Activity

            People

            • Assignee:
              rkanter Robert Kanter
              Reporter:
              rkanter Robert Kanter
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: