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

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-10819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519292#comment-14519292 ] 

Hadoop QA commented on AMBARI-10819:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12729096/AMBARI-10819.0.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/2563//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/2563//console

This message is automatically generated.

> 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)