[
https://issues.apache.org/jira/browse/HADOOP-5726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705591#action_12705591
]
Hemanth Yamijala commented on HADOOP-5726:
------------------------------------------
bq. I'd propose we take this opportunity to further improve the
capacity-scheduler by simplifying it's design, refactoring inner-classes into
standalone classes, using the JobChangeEvents more extensively rather than
re-sort queues on every heartbeat etc. Maybe a new jira?
Arun, I agree. Particularly with the refactoring of inner classes into
standalone classes. Also, I think we should look at combining all queue state
into a single class and promote it to a first class object. Today, this state
is split between JobQueueManager and QueueSchedulingInfo.
Can you please open a new jira with your ideas and we can discuss there ?
> Remove pre-emption from the capacity scheduler code base
> --------------------------------------------------------
>
> Key: HADOOP-5726
> URL: https://issues.apache.org/jira/browse/HADOOP-5726
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/capacity-sched
> Reporter: Hemanth Yamijala
> Assignee: rahul k singh
> Attachments: cs-without-preemption-23-1-2009.patch
>
>
> In an effort to simplify the code base, we would like to remove the
> pre-emption related code in the capacity scheduler. We would reintroduce this
> (possibly with some revisions to the original design) after a while. This
> will be an incompatible change. Any objections ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
