[
https://issues.apache.org/jira/browse/AMBARI-20916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367181#comment-16367181
]
Hudson commented on AMBARI-20916:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8744 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8744/])
AMBARI-20916. Run new heartbeatThread and statusCommand executor instead
(aonishuk:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=cef3f245eed01c36a7e3a9c628040a7b4e7ee1d0])
* (edit) ambari-agent/src/main/python/ambari_agent/ComponentStatusExecutor.py
* (edit) ambari-agent/src/main/python/ambari_agent/HeartbeatThread.py
* (edit) ambari-agent/src/test/python/ambari_agent/TestAgentStompResponses.py
* (edit) ambari-agent/src/main/python/ambari_agent/main.py
> Run new heartbeatThread and statusCommand executor instead of old
> ------------------------------------------------------------------
>
> Key: AMBARI-20916
> URL: https://issues.apache.org/jira/browse/AMBARI-20916
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Priority: Major
> Fix For: 3.0.0
>
> Attachments: AMBARI-20916.patch, AMBARI-20916.patch
>
>
> We have these threads running only in scope of UT. Need to start them on
> ambari-agent start for so testing with ambari-server can be done.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
