[
https://issues.apache.org/jira/browse/HADOOP-3876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618616#action_12618616
]
Vivek Ratan commented on HADOOP-3876:
-------------------------------------
My guess is, we're going to have some 'core' schedulers (which seem appropriate
to belong within the core Hadoop code), and some that are better suited as
contrib projects. We should probably place core schedulers under
_src/mapred/schedulers_. So, for example, the 3445 scheduler would go under
_src/mapred/schedulers/3445_ and the 3746 scheduler under
_src/mapred/schedulers/3746_ (replace '3445' and '3746' with more appropriate
names, if you wish). Others may go in here as well, if its' felt that they're
likely to be deployed in many scenarios, or for whatever other reason. Non-core
schedulers can probably go under contrib.
Another option is to place core schedulers under _src/core/schedulers_, if we
want these to be more than just MR schedulers, but folks may not write non-MR
schedulers for a while. I prefer keeping stuff under _mapred_.
> Hadoop Core should support source filesfor multiple schedulers
> --------------------------------------------------------------
>
> Key: HADOOP-3876
> URL: https://issues.apache.org/jira/browse/HADOOP-3876
> Project: Hadoop Core
> Issue Type: New Feature
> Reporter: Vivek Ratan
>
> Besides the default JT scheduling algorithm, there is work going on with at
> least two more schedulers (HADOOP-3445, HADOOP-3746). HADOOP-3412 makes it
> easier to plug in new schedulers into the JT. Where do we place the source
> files for various schedulers so that it's easy for users to choose their
> scheduler of choice during deployment, and easy for developers to add in more
> schedulers into the framework (without inundating it).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
