hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuan Gong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3700) ATS Web Performance issue at load time when large number of jobs
Date Tue, 26 May 2015 23:36:17 GMT

    [ https://issues.apache.org/jira/browse/YARN-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560124#comment-14560124

Xuan Gong commented on YARN-3700:

bq.5. I don't quite understand to following logic. Why do we want to use ID to set the timestamp?
And how do we verify if we limit the apps num, we are getting the latest apps.

Added testcase in TestApplicationHistoryClientService to verify this. 
In currently test, the teststamp for all the apps is the same. So, I add useID to the timestamp
which could differentiate the timestamp for different apps.  Set the YarnConfiguration.APPLICATION_HISTORY_PREFIX_MAX_APPS
as 1, so we verify that after we call getApplications(), we can get only one application,
and the application is app1 (because the timestamp of app1 is larger then that of app0)

Also, addressed other comments

> ATS Web Performance issue at load time when large number of jobs
> ----------------------------------------------------------------
>                 Key: YARN-3700
>                 URL: https://issues.apache.org/jira/browse/YARN-3700
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager, webapp, yarn
>            Reporter: Xuan Gong
>            Assignee: Xuan Gong
>         Attachments: YARN-3700.1.patch, YARN-3700.2.1.patch, YARN-3700.2.2.patch, YARN-3700.2.patch
> Currently, we will load all the apps when we try to load the yarn timelineservice web
page. If we have large number of jobs, it will be very slow.

This message was sent by Atlassian JIRA

View raw message