Uploaded image for project: 'Falcon'
  1. Falcon
  2. FALCON-378

Feed status fails with NPE post update when the new coordinator is in PREP state

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.4
    • 0.5
    • oozie

    Description

      An NPE is thrown for status calls post feed update briefly between the new coord creation transitioning from PREP to RUNNING at:

      org.apache.falcon.workflow.engine.OozieWorkflowEngine#getCoordActions
                      Date iterEnd = (coord.getNextMaterializedTime().before(end) ? coord.getNextMaterializedTime() : end);
      

      coord.getNextMaterializedTime() is null since the coord is in PREP state as the new coord's effective time is set as now() + 3 min. In reality, this is greater than 3 mins is my observation.

      Feed updated at:
      Current time = Tue, 25 Mar 2014 21:54:00 GMT
      
      Old Coord: 
      Start time = Tue, 25 Mar 2014 00:00:00 GMT
      End time = Tue, 25 Mar 2014 22:00:00 GMT
      Status = RUNNING
      
      New Coord:
      Start time =  Tue, 25 Mar 2014 22:00:00 GMT
      End time = Wed, 26 Mar 2014 00:00:00 GMT
      Status = PREP
      

      Attachments

        1. FALCON-378-v1.patch
          4 kB
          Venkatesh Seetharam
        2. FALCON-378.patch
          4 kB
          Venkatesh Seetharam
        3. test-update-feed.xml
          1 kB
          Venkatesh Seetharam
        4. test-update-feed-1.xml
          1 kB
          Venkatesh Seetharam
        5. oozie-coords.tiff
          124 kB
          Venkatesh Seetharam
        6. oozie-coord-new.tiff
          105 kB
          Venkatesh Seetharam
        7. test-update-feed-2.xml
          1 kB
          Venkatesh Seetharam

        Activity

          People

            svenkat Venkatesh Seetharam
            svenkat Venkatesh Seetharam
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: