Re: [VOTE] Merge feature branch YARN-5734 (API based scheduler configuration) to trunk, branch-3.0, branch-2

Thanks for the votes and discussion. It is now past Monday Oct 9 11:00AM PDT so the vote has ended. There were 4 +1 and no -1, so vote passes. This feature will be merged to trunk, branch-3.0, and branch-2 shortly (16 subtasks). Thanks everyone! Jonathan Hung On Mon, Oct 9, 2017 at 9:18 AM,

Re: [VOTE] Merge feature branch YARN-5734 (API based scheduler configuration) to trunk, branch-3.0, branch-2

+1 (binding) Xuan Gong > >On Mon, Oct 2, 2017 at 11:09 AM, Jonathan Hung >wrote: > >> Hi all, >> >> From discussion at [1], I'd like to start a vote to merge feature branch >> YARN-5734 to trunk, branch-3.0, and branch-2. Vote will be 7 days, >>ending >> Monday Oct 9 at

Re: [VOTE] Merge feature branch YARN-5734 (API based scheduler configuration) to trunk, branch-3.0, branch-2

+1 (binding) I was following this effort closely from the side. The feature proved to be very useful based on our internal use of it. I think it will be beneficial for the community as well. Thanks for working on this Jonathan, Wangda, and everybody involved. --Konstantin On Mon, Oct 2, 2017 at

Re: [VOTE] Merge feature branch YARN-5734 (API based scheduler configuration) to trunk, branch-3.0, branch-2

+1 (Binding), huge thanks to all the other folks spent time to design, development, test and review this feature. In addition to what Jonathan mentioned, all exposed APIs / CLIs are marked as unstable so there should not have backward-compatibility issues. Participated initial design and review

Re: [VOTE] Merge feature branch YARN-5734 (API based scheduler configuration) to trunk, branch-3.0, branch-2

+1 (binding) LinkedIn has been running an internal version of OrgQueue for almost 2 years. It is an essential feature for running YARN scheduler on clusters shared by multiple internal organizations. I have participated in the YARN-5734 design and have regularly synced with Jonathan on

[VOTE] Merge feature branch YARN-5734 (API based scheduler configuration) to trunk, branch-3.0, branch-2

Hi all, >From discussion at [1], I'd like to start a vote to merge feature branch YARN-5734 to trunk, branch-3.0, and branch-2. Vote will be 7 days, ending Monday Oct 9 at 11:00AM PDT. This branch adds a framework to the scheduler to allow scheduler configuration mutation on the fly, including a