hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Azuryy Yu <azury...@gmail.com>
Subject Re: [Proposal] Move schedulers into separate modules
Date Fri, 13 Dec 2013 03:52:14 GMT
Hi Vinod ,
can you file an JIRA for this topic  to discuss, if passed, then you assign
to yourself if you interested,

On Fri, Dec 13, 2013 at 10:44 AM, Vinod Kumar Vavilapalli <
vinodkv@apache.org> wrote:

> Hi all,
> We used to have schedulers as separate modules and thus separate artifacts
> in Hadoop-1. This had many benefits, I am thinking we should do the same now
>  - Separate artifacts: Fast fixes of scheduler-only changes are easy to
> test. Just swap the scheduler jar. One could argue that we can swap the
> resourcemanager jar similarly.
>  - Separate source tree: We can focus more on the stability of
> RM<->Scheduler APIs and interaction. Right now with all the
> scheduler-specific functionality flowing in, in multiple JIRAs, it is
> getting difficult to separate out the core changes from the scheduler
> specific changes.
> It isn't a major change from what we have today, but a major source-move.
> So thought I'll garner opinions.
> Thoughts?
> +Vinod
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message