[
https://issues.apache.org/jira/browse/AMBARI-15123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15155802#comment-15155802
]
Hadoop QA commented on AMBARI-15123:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12788804/AMBARI-15123.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/5490//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/5490//console
This message is automatically generated.
> 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)
