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] [Created] (AMBARI-17510) LogSearch REST Integration component can cause performance issues
Date Thu, 30 Jun 2016 20:27:10 GMT
Robert Nettleton created AMBARI-17510:
-----------------------------------------

             Summary: LogSearch REST Integration component can cause performance issues
                 Key: AMBARI-17510
                 URL: https://issues.apache.org/jira/browse/AMBARI-17510
             Project: Ambari
          Issue Type: Bug
          Components: ambari-server
    Affects Versions: 2.4.0
            Reporter: Robert Nettleton
            Assignee: Robert Nettleton
            Priority: Critical
             Fix For: 2.4.0


In larger clusters, or clusters that are long-running, some performance-related problems have
been uncovered that occur when LogSearch is deployed in an Ambari cluster.

In particular, if the LogSearch Server itself is performing slowly, this can cause a degradation
of service in the Ambari REST API, since the LogSearch integration components make direct
REST calls to obtain the Logging data on behalf of the Ambari UI.  

This problem is caused by two issues:

1. The REST requests occur on the Ambari REST request thread.  This can be problematic if
a given request hangs.  This can cause the Ambari REST API, and the Ambari server itself,
to become unresponsive.

2. The Ambari REST integration layer makes HTTP calls to the LogSearch service to obtain Logging
metadata, that is then attached to the HostComponent resource in Ambari.  These HTTP calls
are not currently configured with a connect or read timeout, which can cause a failing call
to wait indefinitely, which again can cause Ambari to become unresponsive.

I'm working on a fix for this, and will be submitting a patch shortly. 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message