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

Posted to issues@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2017/03/20 21:50:42 UTC

[jira] [Updated] (AMBARI-19530) Deploy Job failed saying "Command aborted. Reason: 'Stage timeout'"

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

Yusaku Sako updated AMBARI-19530:
---------------------------------
    Reporter: Pradarttana  (was: Myroslav Papirkovskyi)

> Deploy Job failed saying "Command aborted. Reason: 'Stage timeout'"
> -------------------------------------------------------------------
>
>                 Key: AMBARI-19530
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19530
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.5.0
>            Reporter: Pradarttana
>            Assignee: Myroslav Papirkovskyi
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19530.patch
>
>
> There's some delay in ActionScheduler between adding cancel command and rescheduled task to agent queue (in case on task timeout).
> If agent sends heartbeat during this delay it will fetch only cancel command, and rescheduled task with next heartbeat only.
> This results in incorrect agent-side processing and fail report



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)