You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@oozie.apache.org by "Mohamed Battisha (Created) (JIRA)" <ji...@apache.org> on 2011/10/31 17:53:32 UTC

[jira] [Created] (OOZIE-591) Oozie continues to materialize new actions after end date modification

Oozie continues to materialize new actions after end date modification
----------------------------------------------------------------------

                 Key: OOZIE-591
                 URL: https://issues.apache.org/jira/browse/OOZIE-591
             Project: Oozie
          Issue Type: New Feature
            Reporter: Mohamed Battisha


Oozie continues to materialize new actions after end date modification. The main issue is related how Oozie materialized the actions based on a FIFO priority queue. Changing the status of a bundle/coordinator job should take higher priority than executing this job.

The main idea is to enable the queue to handle interruptions. Mainly, once you finished what you are working on currently, you should focus on executing this next action.

The issue can be illustrated as follow:

1. Configure a pipeline to run for 1 hour
2. Start the pipeline
3. After it starts materializing new actions, change the end time (in my example - to 10 minutes after the pipeline
starts)
4. Monitor the coordinator apps - they will continue to materialize new actions past the end time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira