Community Articles

Find and share helpful community-sourced technical articles.
Announcements
Celebrating as our community reaches 100,000 members! Thank you!
Labels (1)
avatar
Super Guru

SYMPTOM:

  1. Not able to login to Ambari UI. The Ambari ui was hung.
  2. When checked in logs we found below error -

ERROR:

+++++++ 
16 Sep 2016
13:41:21,377 WARN [qtp-client-10408] ObjectGraphWalker:209 - The configured
limit of 1,000 object references was reached while attempting to calculate the
size of the object graph. Severe performance degradation could occur if the
sizing operation continues. This can be avoided by setting the CacheManger or
Cache <sizeOfPolicy> elements maxDepthExceededBehavior to
"abort" or adding stop points with @IgnoreSizeOf annotations. If
performance degradation is NOT an issue at the configured limit, raise the
limit value using the CacheManager or Cache <sizeOfPolicy> elements
maxDepth attribute. For more information, see the Ehcache configuration
documentation. 
+++++++


ROOT CAUSE: As per above logs we found that the issue is with Ambari cache.

This is related to JIRA - https://issues.apache.org/jira/browse/AMBARI-13517

RESOLUTION: We have two ways to resolve the issue -

==> Disable cache by adding below property in "/etc/ambari-server/conf/ambari.properties" file, and restart the ambari server.

server.timeline.metrics.cache.disabled=true 

$ambari-server restart

==> Increase Ambari server Heap Size

783 Views
Comments
avatar
Super Guru

This is an issue with Ambari version prior to 2.2.0. The article should have clarified it. The JIRA specifies that it is fixed in 2.2.0, however, search engines will not pull this link in searches as such the exposure of the article is extremely limited.

Version history
Last update:
‎12-28-2016 07:13 PM
Updated by:
Contributors