Ambari server log filled with WARN "The configured limit of 1,000 object references was".

[#1]

SYMTOMPS:

Ambari server log shows:

WARN [qtp-client-41858] 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.

WORK-AROUND

Disable cache by setting below property in in /etc/ambari-server/conf/ambari.properties

server.timeline.metrics.cache.disabled = true 

ROOT CAUSE

See: AMBARI-13517

Disabling cache is not going have adverse effect. It was introduced in Ambari 2.1.2 to create a Caching layer that provides sliding window behavior for metric requests to Ambari.