[
https://issues.apache.org/jira/browse/TEZ-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14168016#comment-14168016
]
Prakash Ramachandran edited comment on TEZ-1652 at 10/11/14 5:55 AM:
---------------------------------------------------------------------
[~jeagles] the current swimlanes implementation seems to be using only
startTime, endTime (both can be fetched from events), containerid (should be
available in relatedentities - see TEZ-1655). if we are going with a separate
model for swimlane we can remove otherinfo from the fields requested from the
server further cutting down on the n/w transfer required + serialization costs.
the other options is not to request the otherinfo field while querying data for
swimlanes.
let me know what you think about this.
was (Author: pramachandran):
[~jeagles] the current swimlanes implementation seems to be using only
startTime, endTime (both can be fetched from events), containerid (should be
available in relatedentities - see TEZ-1655). if we are going with a separate
model for swimlane we can remove otherinfo from the fields requested from the
server further cutting down on the n/w transfer required + serialization costs.
let me know what you think about this.
> 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
>
>
> 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)
