ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yusaku Sako (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-4324) Server should rely on command reports when considering tasks timed out
Date Sat, 15 Nov 2014 00:51:34 GMT

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

Yusaku Sako updated AMBARI-4324:
--------------------------------
    Fix Version/s:     (was: 1.7.0)
                   2.0.0

> Server should rely on command reports when considering tasks timed out
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-4324
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4324
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-agent, ambari-server
>    Affects Versions: 1.5.0
>            Reporter: Dmitry Lysnichenko
>            Assignee: Dmitry Lysnichenko
>             Fix For: 2.0.0
>
>
> As of now, task timeout at server and timeout at agent are two different mechanisms,
that currently work independently and duplicate each other. 
> Such behaviour leads to strange scenario:
> - cluster installation is started
> - execution of some command exceeds timeout
> - server considers this command and *all next* commands in request timed out. This state
is shown at UI as well.
> - at the same time, agent considers currently executed command timed out an kills it.
After that, agent starts executing the next command in queue. If next commands does not fail,
agent sends COMPLETE status reports.
> - server receives  COMPLETE status reports and updates component status.
> - if user clicks "Retry installation", only tasks for not installed components are created.
> - as a result, UI shows less tasks than user expects
> h1. Will be fixed by AMBARI-4323



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message