ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myroslav Papirkovskyi (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-19530) Deploy Job failed saying "Command aborted. Reason: 'Stage timeout'"
Date Fri, 13 Jan 2017 16:57:26 GMT

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

Myroslav Papirkovskyi resolved AMBARI-19530.
--------------------------------------------
    Resolution: Fixed

Pushed to trunk and branch-2.5

> 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: Myroslav Papirkovskyi
>            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.4#6332)

Mime
View raw message