[
https://issues.apache.org/jira/browse/AMBARI-9913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14346297#comment-14346297
]
Hudson commented on AMBARI-9913:
--------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #1940 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/1940/])
AMBARI-9913 Ambari Agent failed start blocks all future bootstrap attempts
(fbarca:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=99cc49b784e0abeb754b20e0ea6d24ed7c6d6f3b)
* ambari-agent/src/main/python/ambari_agent/main.py
* ambari-metrics/ambari-metrics-host-monitoring/src/main/python/main.py
> Ambari Agent failed start blocks all future bootstrap attempts
> --------------------------------------------------------------
>
> Key: AMBARI-9913
> URL: https://issues.apache.org/jira/browse/AMBARI-9913
> Project: Ambari
> Issue Type: Bug
> Components: ambari-agent, ambari-metrics
> Affects Versions: 2.0.0
> Reporter: Florian Barca
> Assignee: Florian Barca
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-9913.0.patch
>
>
> Any bootstrap attempt on a machine running the Agent already is going to fail
> because the new Agent session overwrites the existing session's PID file.
> This occurs constantly when backtracking the cluster setup to the host
> registration step, after the hosts have already been registered.
> The Metrics Monitor is exposed to the same kind of behavior.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
