You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@oozie.apache.org by mp...@gmail.com on 2014/06/10 22:21:47 UTC

Oozie REST API: determine if coordinator has running jobs

Hello,

In Oozie 3, when I do this REST query on a coordinator job-id:

GET /oozie/v1/job/0000443-140423173404530-oozie-oozi-C?show=info

the response contains an "actions" array that has a listing of the
workflows:

    "actions": [
        {
            "errorMessage": "",
            "lastModifiedTime": "Wed, 28 May 2014 14:25:08 GMT",
            "createdTime": "Wed, 28 May 2014 14:05:12 GMT",
            "status": "SUCCEEDED",
            "externalStatus": "",
            "type": "",
            "nominalTime": "Wed, 28 May 2014 05:00:00 GMT",
            "externalId": "0000444-140423173404530-oozie-oozi-W",
            "id": "0000443-140423173404530-oozie-oozi-C@1",
            "createdConf": "",
            "missingDependencies": "",
            "runConf": "",
            "actionNumber": 1,
            "errorCode": "",
            "trackerUri": "",
            "toString": "WorkflowAction
name[0000443-140423173404530-oozie-oozi-C@1] status[SUCCEEDED]",
            "coordJobId": "0000443-140423173404530-oozie-oozi-C",
            "consoleUrl": ""
        },
       ...
     ]

When I do that query on against Oozie 4, the actions array is always empty.
 This contradicts what the Oozie 4 REST API documentation states:
https://oozie.apache.org/docs/4.0.0/WebServicesAPI.html

*Is this a bug in Oozie?*

I tried this with "v1" and "v2":

GET /oozie/v1/job/0000443-140423173404530-oozie-oozi-C?show=info
GET /oozie/v2/job/0000443-140423173404530-oozie-oozi-C?show=info

Both return the same thing.

If this is not a bug (and the Oozie 4.0 REST API docs are wrong), then I
need to know how to query Oozie to ask what workflows a coordinator has
run.  What I really need to know is whether a coordinator currently has a
RUNNING workflow.  *How should I do that with Oozie 4?*

I am using the Hortonworks HDP-2.1 distribution of Hadoop and the Oozie
that comes with that, which I believe is Oozie 4.0.0

-Michael

Re: Oozie REST API: determine if coordinator has running jobs

Posted by mp...@gmail.com.
Thanks Shwetha.  That fixed it and it works on both Hadoop 1 and 2 (Oozie
3.3 and Oozie 4).


On Wed, Jun 11, 2014 at 12:45 AM, Shwetha GS <sh...@inmobi.com> wrote:

> Hi Michael,
>
> You need to specify length(number of coordinator actions required in the
> API) with param 'len'. The API also takes an optional 'offset' which is the
> start coordinator action.
>
> -Shwetha
>
>
>
>
> On Wed, Jun 11, 2014 at 1:51 AM, <mp...@gmail.com> wrote:
>
> > Hello,
> >
> > In Oozie 3, when I do this REST query on a coordinator job-id:
> >
> > GET /oozie/v1/job/0000443-140423173404530-oozie-oozi-C?show=info
> >
> > the response contains an "actions" array that has a listing of the
> > workflows:
> >
> >     "actions": [
> >         {
> >             "errorMessage": "",
> >             "lastModifiedTime": "Wed, 28 May 2014 14:25:08 GMT",
> >             "createdTime": "Wed, 28 May 2014 14:05:12 GMT",
> >             "status": "SUCCEEDED",
> >             "externalStatus": "",
> >             "type": "",
> >             "nominalTime": "Wed, 28 May 2014 05:00:00 GMT",
> >             "externalId": "0000444-140423173404530-oozie-oozi-W",
> >             "id": "0000443-140423173404530-oozie-oozi-C@1",
> >             "createdConf": "",
> >             "missingDependencies": "",
> >             "runConf": "",
> >             "actionNumber": 1,
> >             "errorCode": "",
> >             "trackerUri": "",
> >             "toString": "WorkflowAction
> > name[0000443-140423173404530-oozie-oozi-C@1] status[SUCCEEDED]",
> >             "coordJobId": "0000443-140423173404530-oozie-oozi-C",
> >             "consoleUrl": ""
> >         },
> >        ...
> >      ]
> >
> > When I do that query on against Oozie 4, the actions array is always
> empty.
> >  This contradicts what the Oozie 4 REST API documentation states:
> > https://oozie.apache.org/docs/4.0.0/WebServicesAPI.html
> >
> > *Is this a bug in Oozie?*
> >
> > I tried this with "v1" and "v2":
> >
> > GET /oozie/v1/job/0000443-140423173404530-oozie-oozi-C?show=info
> > GET /oozie/v2/job/0000443-140423173404530-oozie-oozi-C?show=info
> >
> > Both return the same thing.
> >
> > If this is not a bug (and the Oozie 4.0 REST API docs are wrong), then I
> > need to know how to query Oozie to ask what workflows a coordinator has
> > run.  What I really need to know is whether a coordinator currently has a
> > RUNNING workflow.  *How should I do that with Oozie 4?*
> >
> > I am using the Hortonworks HDP-2.1 distribution of Hadoop and the Oozie
> > that comes with that, which I believe is Oozie 4.0.0
> >
> > -Michael
> >
>
> --
> _____________________________________________________________
> The information contained in this communication is intended solely for the
> use of the individual or entity to whom it is addressed and others
> authorized to receive it. It may contain confidential or legally privileged
> information. If you are not the intended recipient you are hereby notified
> that any disclosure, copying, distribution or taking any action in reliance
> on the contents of this information is strictly prohibited and may be
> unlawful. If you have received this communication in error, please notify
> us immediately by responding to this email and then delete it from your
> system. The firm is neither liable for the proper and complete transmission
> of the information contained in this communication nor for any delay in its
> receipt.
>

Re: Oozie REST API: determine if coordinator has running jobs

Posted by Shwetha GS <sh...@inmobi.com>.
Hi Michael,

You need to specify length(number of coordinator actions required in the
API) with param 'len'. The API also takes an optional 'offset' which is the
start coordinator action.

-Shwetha




On Wed, Jun 11, 2014 at 1:51 AM, <mp...@gmail.com> wrote:

> Hello,
>
> In Oozie 3, when I do this REST query on a coordinator job-id:
>
> GET /oozie/v1/job/0000443-140423173404530-oozie-oozi-C?show=info
>
> the response contains an "actions" array that has a listing of the
> workflows:
>
>     "actions": [
>         {
>             "errorMessage": "",
>             "lastModifiedTime": "Wed, 28 May 2014 14:25:08 GMT",
>             "createdTime": "Wed, 28 May 2014 14:05:12 GMT",
>             "status": "SUCCEEDED",
>             "externalStatus": "",
>             "type": "",
>             "nominalTime": "Wed, 28 May 2014 05:00:00 GMT",
>             "externalId": "0000444-140423173404530-oozie-oozi-W",
>             "id": "0000443-140423173404530-oozie-oozi-C@1",
>             "createdConf": "",
>             "missingDependencies": "",
>             "runConf": "",
>             "actionNumber": 1,
>             "errorCode": "",
>             "trackerUri": "",
>             "toString": "WorkflowAction
> name[0000443-140423173404530-oozie-oozi-C@1] status[SUCCEEDED]",
>             "coordJobId": "0000443-140423173404530-oozie-oozi-C",
>             "consoleUrl": ""
>         },
>        ...
>      ]
>
> When I do that query on against Oozie 4, the actions array is always empty.
>  This contradicts what the Oozie 4 REST API documentation states:
> https://oozie.apache.org/docs/4.0.0/WebServicesAPI.html
>
> *Is this a bug in Oozie?*
>
> I tried this with "v1" and "v2":
>
> GET /oozie/v1/job/0000443-140423173404530-oozie-oozi-C?show=info
> GET /oozie/v2/job/0000443-140423173404530-oozie-oozi-C?show=info
>
> Both return the same thing.
>
> If this is not a bug (and the Oozie 4.0 REST API docs are wrong), then I
> need to know how to query Oozie to ask what workflows a coordinator has
> run.  What I really need to know is whether a coordinator currently has a
> RUNNING workflow.  *How should I do that with Oozie 4?*
>
> I am using the Hortonworks HDP-2.1 distribution of Hadoop and the Oozie
> that comes with that, which I believe is Oozie 4.0.0
>
> -Michael
>

-- 
_____________________________________________________________
The information contained in this communication is intended solely for the 
use of the individual or entity to whom it is addressed and others 
authorized to receive it. It may contain confidential or legally privileged 
information. If you are not the intended recipient you are hereby notified 
that any disclosure, copying, distribution or taking any action in reliance 
on the contents of this information is strictly prohibited and may be 
unlawful. If you have received this communication in error, please notify 
us immediately by responding to this email and then delete it from your 
system. The firm is neither liable for the proper and complete transmission 
of the information contained in this communication nor for any delay in its 
receipt.