[
https://issues.apache.org/jira/browse/AURORA-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14380587#comment-14380587
]
Bill Farner commented on AURORA-1227:
-------------------------------------
I'm uneasy with the prospect writing code in the scheduler for one-off
nice-to-have aggregations like this. Is there anything preventing this from
being accomplished with the API rather than writing custom code in the
scheduler?
> Create a "top X jobs" debug HTTP endpoint
> -----------------------------------------
>
> Key: AURORA-1227
> URL: https://issues.apache.org/jira/browse/AURORA-1227
> Project: Aurora
> Issue Type: Task
> Components: Scheduler
> Reporter: Maxim Khutornenko
>
> It may be useful to query scheduler for "top X" job names by resource
> utilization (CPU/RAM/DISK) to investigate cluster capacity shortages.
> Something like: /top/\{count\}/\{cpu|ram|disk\}/\{timestamp\} should be able
> to answer questions like "What are the 10 most memory consuming jobs now?" or
> "What were the largest CPU consuming jobs yesterday?" Since we have limited
> task history, answers to latter should be considered as a best effort.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)