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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.2
• Fix Version/s: 2.2.2
• Component/s: stacks
• Assignee: Sumit Mohanty
• Reporter: Sumit Mohanty
• Created: 20/Feb/16 02:06
• Updated: 22/Feb/16 20:14
• Resolved: 22/Feb/16 17:28

Description

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

Issue Links

• is related to: AMBARI-15130 Upgrade alert definition for App Timeline Web UI alert
• links to: Review Board