[
https://issues.apache.org/jira/browse/OOZIE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120474#comment-14120474
]
Purshotam Shah commented on OOZIE-1567:
---------------------------------------
{quote}
In CLI, you can take it in mins. For an automated application on top of oozie,
waiting for mins doesn't work. The java API can take the argument in msecs.
{quote}
Why do you want to poll at msecs? Even getJobInfo API will take few sec to
report status.
In most of case Oozie Job will take at-least few minutes to complete.
As per my experience at Y!. If you expose API, people will start abusing it and
calling server at every msecs will impact server performance and can even bring
it down.
We use getCoordJobInfo API to get job status ,which fetches every column from
DB ( this can be fixed later, we can have a API just to report status).
If users start using api like below, it might bring down DB and Oozie server.
public void pollJob(1864089-140715190315682-oozie-wrkf-C, -1, 5ms, true)
> Provide a wait tool in Oozie
> ----------------------------
>
> Key: OOZIE-1567
> URL: https://issues.apache.org/jira/browse/OOZIE-1567
> Project: Oozie
> Issue Type: New Feature
> Components: core
> Affects Versions: 4.0.0
> Reporter: Viji
> Assignee: Robert Kanter
> Priority: Trivial
> Attachments: OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch,
> OOZIE-1567.patch, OOZIE-1567.patch, OOZIE-1567.patch
>
>
> Currently, in situations where a program has to wait to check wether an oozie
> workflow is successful or not, it is done by constantly pinging the oozie
> workflow status (that is, manual scripts need to be written). It would be
> good if Oozie provided a {{oozie wait -jobID <JOBID>}} or similar.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
