ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-12718) AMS is doing a (Select *) for certain point in time metrics from Dashboard page
Date Tue, 11 Aug 2015 20:42:46 GMT

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

Hudson commented on AMBARI-12718:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.1 #360 (See [https://builds.apache.org/job/Ambari-branch-2.1/360/])
AMBARI-12718 AMS is doing a (Select *) for certain point in time metrics from Dashboard page
(additional patch) (dsen) (dsen: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=913968e37d3c6d6045d0e0522de7ae0442949925)
* ambari-metrics/ambari-metrics-timelineservice/src/test/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/TestPhoenixTransactSQL.java
* ambari-metrics/ambari-metrics-timelineservice/src/main/java/org/apache/hadoop/yarn/server/applicationhistoryservice/metrics/timeline/query/PhoenixTransactSQL.java


> AMS is doing a (Select *) for certain point in time metrics from Dashboard page
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-12718
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12718
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Blocker
>             Fix For: 2.1.1
>
>         Attachments: AMBARI-12718.patch
>
>
> API calls for certain point in time metrics are fetching data for 1 day.
> API:
> {code}
> http://hostname:6188/ws/v1/timeline/metrics?metricNames=dfs.FSNamesystem.MissingReplOneBlocks%2Cdfs.FSNamesystem.TransactionsSinceLastCheckpoint%2Cdfs.FSNamesystem.MillisSinceLastLoadedEdits%2Cdfs.FSNamesystem.SnapshottableDi
rectories%2Cdfs.FSNamesystem.LastCheckpointTime%2Cdfs.FSNamesystem.TotalFiles%2Cmaster.Master.QueueCallTime_median%2Cdfs.FSNamesystem.ExpiredHeartbeats%2Cdfs.FSNamesystem.PostponedMisreplicatedBlocks%2Cdfs.FSNamesystem.LastWrittenTransactionId%2Cdfs.FSNamesystem.Snapshots%2Cjvm.JvmMetrics.MemHeapCommittedM%2Cdfs.FSNamesystem.TransactionsSinceLastLog
Roll%2Cmaster.Server.averageLoad%2Cjvm.JvmMetrics.MemHeapUsedM%2Cdfs.FSNamesystem.PendingDataNodeMessageCount%2Cmaster.AssignmentManger.ritCount%2Cdfs.FSNamesystem.StaleDataNodes&hostname=namenode_hostnamel&appId=NAMENODE
> {code}
> Returned result on a cluster > 1 day old takes very long time.
> The call should return 1 latest value for each metric vs all values.



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

Mime
View raw message