You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Ray Chiang (JIRA)" <ji...@apache.org> on 2016/05/05 23:47:13 UTC

[jira] [Commented] (YARN-5046) [Umbrella] Refactor scheduler code

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

Ray Chiang commented on YARN-5046:
----------------------------------

[~leftnoteasy] or [~jianhe], let me know if you think if it makes sense to make YARN-4433 a sub-task of this JIRA.  I'm also looking at YARN-3890 and YARN-2773 as possible candidates.

> [Umbrella] Refactor scheduler code
> ----------------------------------
>
>                 Key: YARN-5046
>                 URL: https://issues.apache.org/jira/browse/YARN-5046
>             Project: Hadoop YARN
>          Issue Type: Task
>          Components: capacity scheduler, fairscheduler, resourcemanager, scheduler
>    Affects Versions: 3.0.0
>            Reporter: Ray Chiang
>            Assignee: Ray Chiang
>              Labels: technical_debt
>
> At this point in time, there are several places where code common to the schedulers can be moved from one or more of the schedulers into AbstractYARNScheduler or a related interface.
> Creating this umbrella JIRA to track this refactoring.  In general, it is preferable to create a subtask JIRA on a per-method basis.
> This may need some coordination with [YARN-3091  \[Umbrella\] Improve and fix locks of RM scheduler|https://issues.apache.org/jira/browse/YARN-3091].



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org