[ 
https://issues.apache.org/jira/browse/AMBARI-13641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14983460#comment-14983460
 ] 

Hudson commented on AMBARI-13641:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.1 #777 (See 
[https://builds.apache.org/job/Ambari-branch-2.1/777/])
AMBARI-13641. Various metrics show no data available - when HA enabled. 
(swagle: 
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=63daee3b8cee21b64b1af6481ab08dc14637e4c6])
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCacheTest.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricsCacheSizeOfEngine.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricsCacheValue.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCache.java
* 
ambari-server/src/main/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCacheEntryFactory.java
* 
ambari-server/src/test/java/org/apache/ambari/server/controller/metrics/timeline/cache/TimelineMetricCacheSizingTest.java


> Various metrics show no data available - when HA enabled
> --------------------------------------------------------
>
>                 Key: AMBARI-13641
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13641
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics, ambari-server
>    Affects Versions: 2.1.2
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>            Priority: Critical
>             Fix For: 2.1.3
>
>         Attachments: AMBARI-13641.patch
>
>
> The Metrics Cache introduced in Ambari stores the metrics result in an 
> HashMap with metric name as the key. This results in a problem when the same 
> request needs to fetch metrics for both the Namenodes or both the 
> Resourcemangers. The last result gets cached.
> *Note*: Workaround for this is to disable cache in 2.1.2 by setting this 
> property in ambari.properties file : server.timeline.metrics.cache.disabled = 
> true



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to