You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Dmytro Sen (JIRA)" <ji...@apache.org> on 2013/10/30 19:37:26 UTC

[jira] [Updated] (AMBARI-3630) Execution of oozie service check task should be dependent on MR2 service check result.

     [ https://issues.apache.org/jira/browse/AMBARI-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmytro Sen updated AMBARI-3630:
-------------------------------

    Attachment: AMBARI-3630.patch

> Execution of oozie service check task should be dependent on MR2 service check result.
> --------------------------------------------------------------------------------------
>
>                 Key: AMBARI-3630
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3630
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.4.2
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>             Fix For: 1.4.2
>
>         Attachments: AMBARI-3630.patch
>
>
> Start all services call creates multiple tasks. It's observed that oozie service check happens before yarn and MR2 service check. In failure scenario, oozie service check sometimes takes around 535.86 sec to fail.



--
This message was sent by Atlassian JIRA
(v6.1#6144)