Re: [DISCUSS] Merge Absolute resource configuration support in Capacity Scheduler (YARN-5881) to trunk

Thanks everyone for the feedback! Based on positive feedback, we started voting thread in http://mail-archives.apache.org/mod_mbox/hadoop-yarn-dev/201711.mbox/%3CCACYiTuhzMrd_kFRT7_f4VBHejrajbCnVB1wmgHLMLXRr58y0MA%40mail.gmail.com%3E @Carlo: Yes, this change should be straight forward except

Re: [DISCUSS] Merge Absolute resource configuration support in Capacity Scheduler (YARN-5881) to trunk

I haven't tested this, but I support the merge as the patch is very much needed for MS usecases as well... Can this be cherry-picked on 2.9 easily? Thanks for this contribution! Cheers, Carlo On Nov 29, 2017 6:34 PM, "Weiwei Yang" wrote: > Hi Sunil > > +1 from my side.

Re: [DISCUSS] Merge Absolute resource configuration support in Capacity Scheduler (YARN-5881) to trunk

Hi Sunil +1 from my side. Actually we have applied some of these patches to our production cluster since Sep this year, on over 2000+ nodes and it works nicely. +1 for the merge. I am pretty sure this feature will help a lot of users, especially those on cloud. Thanks for getting this done,

Re: [DISCUSS] Merge Absolute resource configuration support in Capacity Scheduler (YARN-5881) to trunk

+1, thanks Sunil for working on this feature! -Rohith Sharma K S On 24 November 2017 at 23:19, Sunil G wrote: > Hi All, > > We would like to bring up the discussion of merging “absolute min/max > resources support in capacity scheduler” branch (YARN-5881) [2] into trunk > in

Re: [DISCUSS] Merge Absolute resource configuration support in Capacity Scheduler (YARN-5881) to trunk

adoop.apache.org>; "mapreduce-...@hadoop.apache.org" < > mapreduce-...@hadoop.apache.org> > Sent: Friday, November 24, 2017 11:49 AM > Subject: [DISCUSS] Merge Absolute resource configuration support in > Capacity Scheduler (YARN-5881) to trunk > > Hi All, > &

Re: [DISCUSS] Merge Absolute resource configuration support in Capacity Scheduler (YARN-5881) to trunk

Thanks Sunil for starting this, +1 from my side. - Wangda On Fri, Nov 24, 2017 at 9:49 AM, Sunil G wrote: > Hi All, > > We would like to bring up the discussion of merging “absolute min/max > resources support in capacity scheduler” branch (YARN-5881) [2] into trunk > in a

[DISCUSS] Merge Absolute resource configuration support in Capacity Scheduler (YARN-5881) to trunk

Hi All, We would like to bring up the discussion of merging “absolute min/max resources support in capacity scheduler” branch (YARN-5881) [2] into trunk in a few weeks. The goal is to get it in for Hadoop 3.1. *Major work happened in this branch* - YARN-6471. Support to add min/max resource