ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Nettleton (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-19105) Ambari LogSearch REST Layer should use a configurable timeout for HTTP connections to LogSearch Server
Date Thu, 15 Dec 2016 23:42:58 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-19105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robert Nettleton updated AMBARI-19105:
--------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Patch merged to trunk and branch-2.5. 

> 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)

Mime
View raw message