You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@oozie.apache.org by ZORAIDA HIDALGO SANCHEZ <zo...@tid.es> on 2014/01/24 10:48:15 UTC
Oozie server does not run as expected when stays idle for a while
Hi all,
our Oozie server sometimes stays idle between submit two different jobs. Our jobs are composed by one coordinator that executes several workflows(one for each directory containing new date). When the server has been idle for a while, only the first workflow is executed and the coordinator keeps RUNNING forever but without continue with the rest of the workflows.If we restart the server then the coordinator continues with the remaining workflows.
Has anyone have the same isuee?
Thanks in advance.
________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
Re: Oozie server does not run as expected when stays idle for a while
Posted by ZORAIDA HIDALGO SANCHEZ <zo...@tid.es>.
Thanks, i will try.
El 01/02/14 14:02, "Harshal Vora" <ha...@gmail.com> escribió:
>Try this configuration.
>
><property>
><name>oozie.service.ActionCheckerService.action.check.delay</name>
><value>60</value>
><description> The time, in seconds, between an ActionCheck for the same
>action. </description>
></property>
>
>
>If I remember correctly, default configuration is 10min.
>Sometimes the callback from hadoop to oozie does not work when a hadoop
>job completes due to some network configurations.
>Hence even if hadoop job completes oozie just waits.
>
>Regards,
>
>On Saturday 01 February 2014 12:01 AM, Mona Chitnis wrote:
>> Hi,
>>
>> I¹ve not encountered this problem before. To understand the symptoms
>> better, can you please share your coordinator definition?
>>
>> Also, are other factors coming into play e.g. Hadoop resources not
>>enough,
>> do you restart Hadoop as well along with Oozie?
>>
>> ‹Mona
>>
>> On 1/31/14, 4:16 AM, "ZORAIDA HIDALGO SANCHEZ" <zo...@tid.es> wrote:
>>
>>> Hi! nothing here?
>>>
>>> El 24/01/14 10:48, "ZORAIDA HIDALGO SANCHEZ" <zo...@tid.es> escribió:
>>>
>>>> Hi all,
>>>>
>>>> our Oozie server sometimes stays idle between submit two different
>>>>jobs.
>>>> Our jobs are composed by one coordinator that executes several
>>>> workflows(one for each directory containing new date). When the server
>>>> has been idle for a while, only the first workflow is executed and the
>>>> coordinator keeps RUNNING forever but without continue with the rest
>>>>of
>>>> the workflows.If we restart the server then the coordinator continues
>>>> with the remaining workflows.
>>>>
>>>> Has anyone have the same isuee?
>>>>
>>>> Thanks in advance.
>>>>
>>>> ________________________________
>>>>
>>>> Este mensaje se dirige exclusivamente a su destinatario. Puede
>>>>consultar
>>>> nuestra política de envío y recepción de correo electrónico en el
>>>>enlace
>>>> situado más abajo.
>>>> This message is intended exclusively for its addressee. We only send
>>>>and
>>>> receive email on the basis of the terms set out at:
>>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>>>
>>> ________________________________
>>>
>>> Este mensaje se dirige exclusivamente a su destinatario. Puede
>>>consultar
>>> nuestra política de envío y recepción de correo electrónico en el
>>>enlace
>>> situado más abajo.
>>> This message is intended exclusively for its addressee. We only send
>>>and
>>> receive email on the basis of the terms set out at:
>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>
________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
Re: Oozie server does not run as expected when stays idle for a while
Posted by Harshal Vora <ha...@gmail.com>.
Try this configuration.
<property>
<name>oozie.service.ActionCheckerService.action.check.delay</name>
<value>60</value>
<description> The time, in seconds, between an ActionCheck for the same
action. </description>
</property>
If I remember correctly, default configuration is 10min.
Sometimes the callback from hadoop to oozie does not work when a hadoop
job completes due to some network configurations.
Hence even if hadoop job completes oozie just waits.
Regards,
On Saturday 01 February 2014 12:01 AM, Mona Chitnis wrote:
> Hi,
>
> I¹ve not encountered this problem before. To understand the symptoms
> better, can you please share your coordinator definition?
>
> Also, are other factors coming into play e.g. Hadoop resources not enough,
> do you restart Hadoop as well along with Oozie?
>
> ‹Mona
>
> On 1/31/14, 4:16 AM, "ZORAIDA HIDALGO SANCHEZ" <zo...@tid.es> wrote:
>
>> Hi! nothing here?
>>
>> El 24/01/14 10:48, "ZORAIDA HIDALGO SANCHEZ" <zo...@tid.es> escribió:
>>
>>> Hi all,
>>>
>>> our Oozie server sometimes stays idle between submit two different jobs.
>>> Our jobs are composed by one coordinator that executes several
>>> workflows(one for each directory containing new date). When the server
>>> has been idle for a while, only the first workflow is executed and the
>>> coordinator keeps RUNNING forever but without continue with the rest of
>>> the workflows.If we restart the server then the coordinator continues
>>> with the remaining workflows.
>>>
>>> Has anyone have the same isuee?
>>>
>>> Thanks in advance.
>>>
>>> ________________________________
>>>
>>> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
>>> nuestra política de envío y recepción de correo electrónico en el enlace
>>> situado más abajo.
>>> This message is intended exclusively for its addressee. We only send and
>>> receive email on the basis of the terms set out at:
>>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>>
>> ________________________________
>>
>> Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
>> nuestra política de envío y recepción de correo electrónico en el enlace
>> situado más abajo.
>> This message is intended exclusively for its addressee. We only send and
>> receive email on the basis of the terms set out at:
>> http://www.tid.es/ES/PAGINAS/disclaimer.aspx
Re: Oozie server does not run as expected when stays idle for a
while
Posted by Mona Chitnis <ch...@yahoo-inc.com>.
Hi,
I¹ve not encountered this problem before. To understand the symptoms
better, can you please share your coordinator definition?
Also, are other factors coming into play e.g. Hadoop resources not enough,
do you restart Hadoop as well along with Oozie?
‹Mona
On 1/31/14, 4:16 AM, "ZORAIDA HIDALGO SANCHEZ" <zo...@tid.es> wrote:
>Hi! nothing here?
>
>El 24/01/14 10:48, "ZORAIDA HIDALGO SANCHEZ" <zo...@tid.es> escribió:
>
>>Hi all,
>>
>>our Oozie server sometimes stays idle between submit two different jobs.
>>Our jobs are composed by one coordinator that executes several
>>workflows(one for each directory containing new date). When the server
>>has been idle for a while, only the first workflow is executed and the
>>coordinator keeps RUNNING forever but without continue with the rest of
>>the workflows.If we restart the server then the coordinator continues
>>with the remaining workflows.
>>
>>Has anyone have the same isuee?
>>
>>Thanks in advance.
>>
>>________________________________
>>
>>Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
>>nuestra política de envío y recepción de correo electrónico en el enlace
>>situado más abajo.
>>This message is intended exclusively for its addressee. We only send and
>>receive email on the basis of the terms set out at:
>>http://www.tid.es/ES/PAGINAS/disclaimer.aspx
>
>
>________________________________
>
>Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
>nuestra política de envío y recepción de correo electrónico en el enlace
>situado más abajo.
>This message is intended exclusively for its addressee. We only send and
>receive email on the basis of the terms set out at:
>http://www.tid.es/ES/PAGINAS/disclaimer.aspx
Re: Oozie server does not run as expected when stays idle for a while
Posted by ZORAIDA HIDALGO SANCHEZ <zo...@tid.es>.
Hi! nothing here?
El 24/01/14 10:48, "ZORAIDA HIDALGO SANCHEZ" <zo...@tid.es> escribió:
>Hi all,
>
>our Oozie server sometimes stays idle between submit two different jobs.
>Our jobs are composed by one coordinator that executes several
>workflows(one for each directory containing new date). When the server
>has been idle for a while, only the first workflow is executed and the
>coordinator keeps RUNNING forever but without continue with the rest of
>the workflows.If we restart the server then the coordinator continues
>with the remaining workflows.
>
>Has anyone have the same isuee?
>
>Thanks in advance.
>
>________________________________
>
>Este mensaje se dirige exclusivamente a su destinatario. Puede consultar
>nuestra política de envío y recepción de correo electrónico en el enlace
>situado más abajo.
>This message is intended exclusively for its addressee. We only send and
>receive email on the basis of the terms set out at:
>http://www.tid.es/ES/PAGINAS/disclaimer.aspx
________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx