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

Posted to dev@ambari.apache.org by "Florian Barca (JIRA)" <ji...@apache.org> on 2015/04/29 10:24:06 UTC

[jira] [Updated] (AMBARI-10819) Ambari bootstrap: Premature Agent shutdown may lead to Agent stall

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

Florian Barca updated AMBARI-10819:
-----------------------------------
    Attachment: AMBARI-10819.0.patch

Removed the agent stop invocation. The agent restarts now only after all the bits have been deployed.

> Ambari bootstrap: Premature Agent shutdown may lead to Agent stall
> ------------------------------------------------------------------
>
>                 Key: AMBARI-10819
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10819
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-agent, ambari-server
>    Affects Versions: 2.1.0
>         Environment: Linux all versions
>            Reporter: Florian Barca
>            Assignee: Florian Barca
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10819.0.patch
>
>
> Currently, the bootstrap script shuts down the existing Agent before attempting anything else. This is a problem, as any bug/malfunction that terminates the execution before the new Agent is set up risks to leave the old Agent stopped, so the machine becomes unresponsive. The logic needs to account for potential failures and only restart the Agent after all the bits have been deployed and the configuration has been properly set.



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