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)
