[
https://issues.apache.org/jira/browse/OOZIE-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037116#comment-14037116
]
Shwetha G S commented on OOZIE-1863:
------------------------------------
Since dryRun doesn't store anything in DB, it can be done independently without
design change?
> Bundle submit should fail without submitting any coord if one of coord has
> issue
> --------------------------------------------------------------------------------
>
> Key: OOZIE-1863
> URL: https://issues.apache.org/jira/browse/OOZIE-1863
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
>
> Currently, bundle submit command queues coord submit for all coords.
> StatusTransitService, which normally runs after 5 min check the status of
> each submitted coord and if any of them has failed, it kills running bundle.
> This approach has two issue
> a. Bundle is status is shown as "killed" ( few submitted coord is also
> killed). It will be difficult for user to find out the root cause.
> b. Few of the coord will be in running state for sometime and might corrupt
> or produce stale data.
> Bundle submit should dryrun coord before queuing submit command.
> We can further improve the bundle job submission logic.
> We can call CoordSubmitXCommand synchronously and if any coord submit fails (
> bcz of DB or other evn issues), kill other submitted coord jobs.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
