***UNCHECKED*** Re: [DISCUSS] Merge YARN-6592 to trunk

2018-01-26 Thread Arun Suresh
Thanks everyone. I've opened a VOTE thread.. @Carlo Interesting idea to support Kubernates API. Definitely makes sense. My understanding is that we can emulate specification for a k8 POD within our scheme of things by assigning the same source tag to a set of scheduling requests. Ill dig in to thi

Re: [DISCUSS] Merge YARN-6592 to trunk

2018-01-26 Thread Carlo Aldo Curino
Also I think this can help us close the gap (and surpass) Kubernetes for complex services (at least for resource management)... It would be awesome to have a compatibility layer so folks can run Kubernetes natives apps on a yarn cluster. On Jan 26, 2018 1:32 AM, "Carlo Aldo Curino" wrote: +1.

Re: [DISCUSS] Merge YARN-6592 to trunk

2018-01-26 Thread Carlo Aldo Curino
+1. I didn't runs tests, but I like the design, and speaking with ops teams that operate large clusters I hear this is a feature they think is going to help a lot, so I am very supportive of this effort. On Jan 25, 2018 7:08 PM, "Konstantinos Karanasos" wrote: > Thanks for starting the thread Ar

Re: [DISCUSS] Merge YARN-6592 to trunk

2018-01-25 Thread Konstantinos Karanasos
Thanks for starting the thread Arun, +1 from me too. Konstantinos On Thu, Jan 25, 2018 at 18:54 Weiwei Yang wrote: > +1, thanks for getting to this milestone Arun. > I’ve done some basic validations on a 4 nodes cluster, with some general > affinity/anti-affinty/cardinality constraints, it work

Re: [DISCUSS] Merge YARN-6592 to trunk

2018-01-25 Thread Weiwei Yang
+1, thanks for getting to this milestone Arun. I’ve done some basic validations on a 4 nodes cluster, with some general affinity/anti-affinty/cardinality constraints, it worked. I’ve also reviewed the doc, it’s in good shape and very illustrative. Thanks. -- Weiwei On 26 Jan 2018, 10:44 AM +08

Re: [DISCUSS] Merge YARN-6592 to trunk

2018-01-25 Thread Sunil G
+1. Thanks Arun. I did manual testing for check affinity and anti-affinity features with placement allocator. Also checked SLS to see any performance regression, and there are not much difference as Arun mentioned. Thanks all the folks for working on this. Kudos! - Sunil On Fri, Jan 26, 2018

Re: [DISCUSS] Merge YARN-6592 to trunk

2018-01-25 Thread Wangda Tan
Thanks Arun +1, Best, Wangda On Fri, Jan 26, 2018 at 7:46 AM, Arun Suresh wrote: > Hello yarn-dev@ > > We feel that the YARN-6592 dev branch mostly in shape to be merged into > trunk. This branch adds support for placing containers in YARN using rich > placement constraints. For example, this

[DISCUSS] Merge YARN-6592 to trunk

2018-01-25 Thread Arun Suresh
Hello yarn-dev@ We feel that the YARN-6592 dev branch mostly in shape to be merged into trunk. This branch adds support for placing containers in YARN using rich placement constraints. For example, this can be used by applications to co-locate containers on a node or rack (*affinity *constraint),