Return-Path: 
 <dev-return-108377-apmail-ambari-dev-archive=ambari.apache.org@ambari.apache.org>
X-Original-To: apmail-ambari-dev-archive@www.apache.org
Delivered-To: apmail-ambari-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 82E9818F77
	for <apmail-ambari-dev-archive@www.apache.org>;
 Sat, 20 Feb 2016 02:07:18 +0000 (UTC)
Received: (qmail 58473 invoked by uid 500); 20 Feb 2016 02:07:18 -0000
Delivered-To: apmail-ambari-dev-archive@ambari.apache.org
Received: (qmail 58439 invoked by uid 500); 20 Feb 2016 02:07:18 -0000
Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@ambari.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@ambari.apache.org>
List-Post: <mailto:dev@ambari.apache.org>
List-Id: <dev.ambari.apache.org>
Reply-To: dev@ambari.apache.org
Delivered-To: mailing list dev@ambari.apache.org
Received: (qmail 58414 invoked by uid 99); 20 Feb 2016 02:07:18 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Feb 2016 02:07:18 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 0D8D12C14F0
	for <dev@ambari.apache.org>; Sat, 20 Feb 2016 02:07:18 +0000 (UTC)
Date: Sat, 20 Feb 2016 02:07:18 +0000 (UTC)
From: "Sumit Mohanty (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12940730.1455933987000.99622.1455934038050@Atlassian.JIRA>
In-Reply-To: <JIRA.12940730.1455933987000@Atlassian.JIRA>
References: <JIRA.12940730.1455933987000@Atlassian.JIRA>
 <JIRA.12940730.1455933987954@arcas>
Subject: [jira] [Created] (AMBARI-15123) Ambari's App Timeline Web UI Alert
 tries make http heavy call timelineserver:httpPort which can also cause OOM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

Sumit Mohanty created AMBARI-15123:
--------------------------------------

             Summary: Ambari's App Timeline Web UI Alert tries make http heavy call timelineserver:httpPort which can also cause OOM
                 Key: AMBARI-15123
                 URL: https://issues.apache.org/jira/browse/AMBARI-15123
             Project: Ambari
          Issue Type: Bug
          Components: stacks
    Affects Versions: 2.2.2
            Reporter: Sumit Mohanty
            Assignee: Sumit Mohanty
             Fix For: 2.2.2
         Attachments: AMBARI-15123.patch

Ambari's App Timeline Web UI Alert tries make http heavy call timelineserver:httpPort which can also cause OOM

Hit this issue while testing ATS v1.5 on 32 node cluster under load was going OOM, we discovered there are instance where <ATSHost:webPort> is being hit.

Looks like Ambari's App Timeline Web UI alerting system is trying call it
As from Ambari Alerts we can see error like "Connection failed to http://ATS_HOST:8188 (timed out)"

Now If we try hit http://<ATSHost>:<webappPort>, by default It load http://<ATSHost>:<webappPort>/applicationhistory 
e.g.  Accessing http://ATS_HOST:8188 will try to access http:/ATS_HOST:8188/applicationhistory page.
If cluster has AHS/GHS enabled (under ATS), then this call result heavy html containing large of application.

We can make alert to access some lightweight call like: http://<ATSHost>:<webappPort>/applicationhistory/about, or http://<ATSHost>:<webappPort>/ws/v1/timeline
e.g.  http://ATS_HOST:8188/applicationhistory/about
or 
http://ATS_HOST:8188/ws/v1/timeline



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