[
https://issues.apache.org/jira/browse/OOZIE-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sandeep samudrala updated OOZIE-2711:
-------------------------------------
Description:
At times user would want to update the coordinator end time to some time in the
past but not delete the instances from the specified end time to current time.
This way, when a new coordinator starts from the specified end time gives
capability to user to track new coord flow with new changes from an EFFECTIVE
time and not on current time(currently end time can be set at most to current
time) as any instances that are succeeded in the past end time cannot be
updated.
While updating the end time of a coordinator, the coordinator is paused (by
sending pause time), which means the end time can be future only as
coordchangecommandx checks for the instances to be deleted to be in
WAITING/READY.
I propose to add this capability to add end time to past, but not delete any
instance between the specified time and the current time and also mark these
instances to a new FINAL state, where these instances cannot be rerun or
changed state to unless the coord end time is being changed to future.
This will keep the identity of the instances that have already run/succeeded,
and also enable user to start new coord for the same application with user
applicable changes to kick in from the specified time. The FINAL state ensures
that there are no multiple instances for a given nominal time that are
available for rerun/retry etc.
was:
At times user would want to update the coordinator end time to some time in the
past but not delete the instances from the specified end time to current time.
This way, when a new coordinator starts from the specified end time gives
capability to user to track new coord flow with new changes from an EFFECTIVE
time and not on current time(currently end time can be set at most to current
time) as any instances that are succeeded in the past end time cannot be
updated.
While updating the end time of a coordinator, the coordinator is paused (by
sending pause time), which means the end time can be future only as
coordchangecommandx checks for the instances to be deleted to be in
WAITING/READY.
> Ability to set end time of coordinator to time in the past.
> -----------------------------------------------------------
>
> Key: OOZIE-2711
> URL: https://issues.apache.org/jira/browse/OOZIE-2711
> Project: Oozie
> Issue Type: Improvement
> Reporter: sandeep samudrala
>
> At times user would want to update the coordinator end time to some time in
> the past but not delete the instances from the specified end time to current
> time. This way, when a new coordinator starts from the specified end time
> gives capability to user to track new coord flow with new changes from an
> EFFECTIVE time and not on current time(currently end time can be set at most
> to current time) as any instances that are succeeded in the past end time
> cannot be updated.
> While updating the end time of a coordinator, the coordinator is paused (by
> sending pause time), which means the end time can be future only as
> coordchangecommandx checks for the instances to be deleted to be in
> WAITING/READY.
> I propose to add this capability to add end time to past, but not delete any
> instance between the specified time and the current time and also mark these
> instances to a new FINAL state, where these instances cannot be rerun or
> changed state to unless the coord end time is being changed to future.
> This will keep the identity of the instances that have already run/succeeded,
> and also enable user to start new coord for the same application with user
> applicable changes to kick in from the specified time. The FINAL state
> ensures that there are no multiple instances for a given nominal time that
> are available for rerun/retry etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
