[
https://issues.apache.org/jira/browse/AMBARI-18505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15535850#comment-15535850
]
Hadoop QA commented on AMBARI-18505:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12831086/AMBARI-18505.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/8777//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8777//console
This message is automatically generated.
> Ambari Status commands should enforce a timeout < heartbeat interval
> --------------------------------------------------------------------
>
> Key: AMBARI-18505
> URL: https://issues.apache.org/jira/browse/AMBARI-18505
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.4.2
>
> Attachments: AMBARI-18505.patch
>
>
> SmartSense status command does an http call without timeout in 1.2 version of
> SS.
> Ambari agent queues STATUS commands until we end up with HB lost state with
> ton of commands queued up.
> This should just never happen is commands are getting queued by by the agent
> every HB.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
