[
https://issues.apache.org/jira/browse/TEZ-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342715#comment-14342715
]
Jonathan Eagles commented on TEZ-1652:
--------------------------------------
[~Sreenath], [~pramachandran], looking for some help with this patch. I have
implemented the lighter weight task_attempt -> swimlane_task_attempt that will
allow to render 3000 (likely 5000-1000) task attempts in a reasonable time. I
have switched to loading the model from the route to the controller and have
made much progress in bring the swimlane design in line with the graph view
design. Please have a review so I can make this patch even better. I plan on
bringing the swimlane view fully in line with dag graph view, but the main
purpose of this patch is to support large numbers of task.
> Large job support for Swimlane view
> -----------------------------------
>
> Key: TEZ-1652
> URL: https://issues.apache.org/jira/browse/TEZ-1652
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Jonathan Eagles
> Assignee: Jonathan Eagles
> Attachments: TEZ-1652-v1.patch, TEZ-1652.1.patch, TEZ-1652.2.patch
>
>
> Issue is that by default, Timeline Server only returns 100 max entity results
> per query. For query for all task attempts for dag. A limit should be high
> enough to get all entries and yet provide responsiveness.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
