[
https://issues.apache.org/jira/browse/TEZ-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278040#comment-14278040
]
Hitesh Shah commented on TEZ-1942:
----------------------------------
[~pramachandran] Looks like we need to add primary filters to the entities on
every call to timeline as per the conversation on YARN-3062. Seems like a very
lame solution but probably the only way to get the UI to work correctly against
timeline data.
Would you like to take a crack at this?
> Number of tasks show in Tez UI with auto-reduce parallelism is misleading
> -------------------------------------------------------------------------
>
> Key: TEZ-1942
> URL: https://issues.apache.org/jira/browse/TEZ-1942
> Project: Apache Tez
> Issue Type: Bug
> Affects Versions: 0.5.2
> Reporter: Rajesh Balamohan
> Attachments: Screen Shot 2015-01-14 at 9.18.21 AM.png, Screen Shot
> 2015-01-14 at 9.18.54 AM.png, output.json, result_with_direct_vertex.png,
> result_with_primary_filter.png
>
>
> Ran a simple hive query (with tez) and "--hiveconf
> hive.tez.auto.reducer.parallelism=true" . This internally turns on tez's
> auto reduce parallelism.
> - Job started off with 1009 reduce tasks
> - Tez reduces the number of reducers to 253
> - Job completes successfully, but TEZ UI shows 1009 as the number of reducers
> (and 253 tasks as successful tasks). This can be a little misleading.
> I will attach the screenshots soon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
