[
https://issues.apache.org/jira/browse/AMBARI-15277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177345#comment-15177345
]
Hadoop QA commented on AMBARI-15277:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12791089/AMBARI-15277.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
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/5697//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5697//console
This message is automatically generated.
> Increase timeout in Accumulo service check
> ------------------------------------------
>
> Key: AMBARI-15277
> URL: https://issues.apache.org/jira/browse/AMBARI-15277
> Project: Ambari
> Issue Type: Improvement
> Components: stacks
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: trunk, 2.2.2
>
> Attachments: AMBARI-15277.patch
>
>
> I was just looking at the logs for a single-node installation which had a
> service check failure for Accumulo. Looking at the logs, nothing was
> inherently wrong with Accumulo, it just took longer than the timeout was set
> for.
> We should increase the timeout to avoid failing the service check for
> (ultimately) no reason.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
