[
https://issues.apache.org/jira/browse/TEZ-2923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15004854#comment-15004854
]
Hitesh Shah commented on TEZ-2923:
----------------------------------
Agreed that if the vertex cache has expired, it will do a full scan. My line of
thinking was that if the user either looks up the DAG or the Vertex, we will
not end up doing 2 scans of all tasks when the vertex is running. There could
be some minimal benefit of caching the vertex counters and re-using them at the
dag level ( consider a case where user view dag counters and then clicks
through to a particular vertex ).
In any case, I am not sure how much of a benefit there is. We can go with a
current implementation for now and look at using the vertex cached counters
later based on additional profiling.
> Tez Live UI counters view empty for vertices, tasks, attempts
> -------------------------------------------------------------
>
> Key: TEZ-2923
> URL: https://issues.apache.org/jira/browse/TEZ-2923
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Jonathan Eagles
> Assignee: Jonathan Eagles
> Attachments: TEZ-2293.1.patch, TEZ-2923.2.patch, TEZ-2923.3.patch,
> TEZ-2923.4.patch, TEZ-2923.5.patch, TEZ-2923.6.patch
>
>
> Vertex Counters, Task Counters, and TaskAttempt Counters views are blank
> during the live tez AM view. This is due to the nature of the request sent by
> the Tez UI to the Tez AM rest api. The api only accepts a list of counter
> groups or counter names, since the groups and names are unknown at the time
> of the request, there is no away to ask for counters by name. This jira
> proposes to allow for a "*" to the rest api to request all counters to be
> returned.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
