You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@oozie.apache.org by Richard Ross <ri...@gmail.com> on 2014/02/20 13:11:47 UTC
Coordinator action TIMEDOUT when no timeout is set
Hey:
Yesterday I setup a daily coordinator with an input dataset. It is scheduled to run everyday at 00:00 and process the dataset. I don't have the piece that creates the dataset automated yet, and was planning to manually create the dataset each morning while I work on the automation pieces. (This would help me prove that the data processing piece works.) Since I did not set a timeout on the coordinator and the default timeout is never, I thought the coordinator action would wait until I created the dataset some hours later. When I checked this morning, the coordinator action for today was in a TIMEDOUT state. A snippet of the logs shows that it timed out at 2014-02-20 02:01:05,169:
2014-02-20 02:01:05,169 INFO CoordActionNotificationXCommand:539 - USER[-] GROUP[-] TOKEN[-] APP[-] JOB[0000020-140124104310682-oozie-oozi-C] ACTION[0000020-140124104310682-oozie-oozi-C@1] STARTED Coordinator Notification actionId=0000020-140124104310682-oozie-oozi-C@1 : TIMEDOUT
2014-02-20 02:01:05,170 INFO CoordActionNotificationXCommand:539 - USER[-] GROUP[-] TOKEN[-] APP[-] JOB[0000020-140124104310682-oozie-oozi-C] ACTION[0000020-140124104310682-oozie-oozi-C@1] No Notification URL is defined. Therefore nothing to notify for job 0000020-140124104310682-oozie-oozi-C action ID 0000020-140124104310682-oozie-oozi-C@1
2014-02-20 02:01:05,170 INFO CoordActionNotificationXCommand:539 - USER[-] GROUP[-] TOKEN[-] APP[-] JOB[0000020-140124104310682-oozie-oozi-C] ACTION[0000020-140124104310682-oozie-oozi-C@1] ENDED Coordinator Notification actionId=0000020-140124104310682-oozie-oozi-C@1
I did create the dataset and the done-flag, and that didn't get it going either.
Any ideas what's going on?
Thanks in advance,
Richard.
RE: Coordinator action TIMEDOUT when no timeout is set
Posted by "Ross, Richard" <ri...@truvenhealth.com>.
Thanks, Mona. This is easy to fix.
Richard.
-----Original Message-----
From: Mona Chitnis [mailto:chitnis@yahoo-inc.com]
Sent: Thursday, February 20, 2014 3:49 PM
To: user@oozie.apache.org
Subject: Re: Coordinator action TIMEDOUT when no timeout is set
Hi Richard,
The default timeout is in fact changed from -1 (infinity) to 2 hours, to avoid unnecessary CPU cycles to check for nonexistent data.
Property in oozie-site.xml
<property>
<name>oozie.service.coord.normal.default.timeout
</name>
<value>120</value>
<description>Default timeout for a coordinator action input check (in
minutes) for normal job.
-1 means infinite timeout</description>
</property>
Sorry the documentation does not reflect this change. Will fix this in the next release doc. So for now, please put -1 there for your testing purposes.
On 2/20/14, 4:11 AM, "Richard Ross" <ri...@gmail.com> wrote:
>Hey:
>
>Yesterday I setup a daily coordinator with an input dataset. It is
>scheduled to run everyday at 00:00 and process the dataset. I don't
>have the piece that creates the dataset automated yet, and was planning
>to manually create the dataset each morning while I work on the
>automation pieces. (This would help me prove that the data processing
>piece works.) Since I did not set a timeout on the coordinator and the
>default timeout is never, I thought the coordinator action would wait
>until I created the dataset some hours later. When I checked this
>morning, the coordinator action for today was in a TIMEDOUT state. A
>snippet of the logs shows that it timed out at 2014-02-20 02:01:05,169:
>
>2014-02-20 02:01:05,169 INFO CoordActionNotificationXCommand:539 -
>USER[-] GROUP[-] TOKEN[-] APP[-]
>JOB[0000020-140124104310682-oozie-oozi-C]
>ACTION[0000020-140124104310682-oozie-oozi-C@1] STARTED Coordinator
>Notification actionId=0000020-140124104310682-oozie-oozi-C@1 : TIMEDOUT
>2014-02-20 02:01:05,170 INFO CoordActionNotificationXCommand:539 -
>USER[-] GROUP[-] TOKEN[-] APP[-]
>JOB[0000020-140124104310682-oozie-oozi-C]
>ACTION[0000020-140124104310682-oozie-oozi-C@1] No Notification URL is
>defined. Therefore nothing to notify for job
>0000020-140124104310682-oozie-oozi-C action ID
>0000020-140124104310682-oozie-oozi-C@1
>2014-02-20 02:01:05,170 INFO CoordActionNotificationXCommand:539 -
>USER[-] GROUP[-] TOKEN[-] APP[-]
>JOB[0000020-140124104310682-oozie-oozi-C]
>ACTION[0000020-140124104310682-oozie-oozi-C@1] ENDED Coordinator
>Notification actionId=0000020-140124104310682-oozie-oozi-C@1
>
>I did create the dataset and the done-flag, and that didn't get it
>going either.
>
>Any ideas what's going on?
>
>Thanks in advance,
>Richard.
Re: Coordinator action TIMEDOUT when no timeout is set
Posted by Mona Chitnis <ch...@yahoo-inc.com>.
Hi Richard,
The default timeout is in fact changed from -1 (infinity) to 2 hours, to
avoid unnecessary CPU cycles to check for nonexistent data.
Property in oozie-site.xml
<property>
<name>oozie.service.coord.normal.default.timeout
</name>
<value>120</value>
<description>Default timeout for a coordinator action input check (in
minutes) for normal job.
-1 means infinite timeout</description>
</property>
Sorry the documentation does not reflect this change. Will fix this in the
next release doc. So for now, please put -1 there for your testing
purposes.
On 2/20/14, 4:11 AM, "Richard Ross" <ri...@gmail.com> wrote:
>Hey:
>
>Yesterday I setup a daily coordinator with an input dataset. It is
>scheduled to run everyday at 00:00 and process the dataset. I don't have
>the piece that creates the dataset automated yet, and was planning to
>manually create the dataset each morning while I work on the automation
>pieces. (This would help me prove that the data processing piece works.)
>Since I did not set a timeout on the coordinator and the default timeout
>is never, I thought the coordinator action would wait until I created the
>dataset some hours later. When I checked this morning, the coordinator
>action for today was in a TIMEDOUT state. A snippet of the logs shows
>that it timed out at 2014-02-20 02:01:05,169:
>
>2014-02-20 02:01:05,169 INFO CoordActionNotificationXCommand:539 -
>USER[-] GROUP[-] TOKEN[-] APP[-]
>JOB[0000020-140124104310682-oozie-oozi-C]
>ACTION[0000020-140124104310682-oozie-oozi-C@1] STARTED Coordinator
>Notification actionId=0000020-140124104310682-oozie-oozi-C@1 : TIMEDOUT
>2014-02-20 02:01:05,170 INFO CoordActionNotificationXCommand:539 -
>USER[-] GROUP[-] TOKEN[-] APP[-]
>JOB[0000020-140124104310682-oozie-oozi-C]
>ACTION[0000020-140124104310682-oozie-oozi-C@1] No Notification URL is
>defined. Therefore nothing to notify for job
>0000020-140124104310682-oozie-oozi-C action ID
>0000020-140124104310682-oozie-oozi-C@1
>2014-02-20 02:01:05,170 INFO CoordActionNotificationXCommand:539 -
>USER[-] GROUP[-] TOKEN[-] APP[-]
>JOB[0000020-140124104310682-oozie-oozi-C]
>ACTION[0000020-140124104310682-oozie-oozi-C@1] ENDED Coordinator
>Notification actionId=0000020-140124104310682-oozie-oozi-C@1
>
>I did create the dataset and the done-flag, and that didn't get it going
>either.
>
>Any ideas what's going on?
>
>Thanks in advance,
>Richard.