[
https://issues.apache.org/jira/browse/TEZ-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063044#comment-15063044
]
Rohini Palaniswamy commented on TEZ-2942:
-----------------------------------------
As [~venkateshrin] pointed out, we can select all the framework counters from
the "All Vertices" page of DAG for comparing across vertices or "Tasks" or
"Task attempts" page of a vertex for comparing across tasks of a vertex. That
covers 90% of the general use cases of drilling down into counters for
investigating issues and performance problems. The rest 10% that is missing as
functionality is the ability to drill down on custom counters (For eg: Pig
counters for spill, multiple output records, etc). On the usability front, the
UI is really good for sorting and looking at counters and that too multiple
counters in fact which is better than MR. But having to load all the other task
columns takes a huge hit on the page loading time (and pressure on ATS memory
to construct the response) considering that most of our average to big jobs
have tasks anywhere from 1000-40K.
> Tez UI: Allow users to drill down into counters
> -----------------------------------------------
>
> Key: TEZ-2942
> URL: https://issues.apache.org/jira/browse/TEZ-2942
> Project: Apache Tez
> Issue Type: Bug
> Components: UI
> Reporter: Jonathan Eagles
>
> One feature gap with MR history server is the ability to drill down into
> counters. A can click on a specific counter in the counter table and see the
> breakdown across tasks. This is most useful in the DAG counters and vertex
> counters views to drill down to understand the breakdown of the counter at
> the level deeper. For example DAG -> Vertex -> Task
> As part of discussion with TEZ-2923, we should enhance the AM counter caching
> since counter drill down can make use of the cache.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
