[
https://issues.apache.org/jira/browse/OOZIE-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14117244#comment-14117244
]
Shwetha G S commented on OOZIE-1567:
------------------------------------
{noformat}
+ Option timeout = new Option(TIMEOUT_OPTION, true, "timeout in seconds
(default is -1 (no timeout))");
+ Option interval = new Option(INTERVAL_OPTION, true, "polling interval
in seconds (default is 60)");
{noformat}
we should give sane default for timeout, just in case the user forgets to stop
if the job is stuck(this will unnecessarily put more load on oozie). Probably
10 mins/1 hour. Depends on the kind of jobs that users typically launch. We use
coord always. So, I don't know the typical workflow usecases
interval depends on workflow usecases again. Pick something thats useful for
most
{noformat}
+ public void pollJob(String id, int timeout, int interval, boolean quiet)
throws OozieClientException {
{noformat}
Its better to expose time in milli secs as long
{noformat}
+ System.out.println(jobInfo.getStatus());
{noformat}
This doesn't print '.'. Is it intentional?
> 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
>
>
> 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)
