You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/05/09 20:41:04 UTC
[jira] [Commented] (AMBARI-20916) Run new heartbeatThread and
statusCommand executor instead of old
[ https://issues.apache.org/jira/browse/AMBARI-20916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003511#comment-16003511 ]
Hadoop QA commented on AMBARI-20916:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12867180/AMBARI-20916.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11576//console
This message is automatically generated.
> 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
> 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
(v6.3.15#6346)