Dmytro Sen created AMBARI-12718:
-----------------------------------

             Summary: 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


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)

Reply via email to