[
https://issues.apache.org/jira/browse/AMBARI-19105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15752533#comment-15752533
]
Hadoop QA commented on AMBARI-19105:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843460/AMBARI-19105.patch.2
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/9700//console
This message is automatically generated.
> Ambari LogSearch REST Layer should use a configurable timeout for HTTP
> connections to LogSearch Server
> ------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-19105
> URL: https://issues.apache.org/jira/browse/AMBARI-19105
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Robert Nettleton
> Assignee: Robert Nettleton
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19105.patch.2
>
>
> The HTTP connection used to make REST calls on the LogSearch Server is
> currently using a hard-coded timeout, which was introduced in:
> AMBARI-17510
> as part of a fix for a performance issue in LogSearch.
> This issue tracks the work to make the connection and read timeouts
> configurable for the LogSearch integration code. These timeouts should be
> configurable in ambari.properties, and should have valid defaults if not set
> by the customer.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
