Hi all,
Given we have 3 binding +1s, the vote passes. I just push changes to trunk.
Will update JIRAs accordingly.
Thanks everybody for helping this feature and voting!
Best,
Wangda
On Sat, Aug 26, 2017 at 8:58 AM, Sunil G wrote:
> Hi Daniel
>
> Thank you very much for
Hi Daniel
Thank you very much for the support.
* When you say that the feature can be turned
off, do you mean resource types or resource profiles? I know there's an
off-by-default property that governs resource profiles, but I didn't see
any way to turn off resource types.
Thanks Arun for checking the feature.
* can you folks point me to any test application / framework or has this
been integrated with MapReduce
Currently this feature is integrated with Distributed Shell.
Reference: YARN-5588
This is not yet integrated with MapReduce. This work is ongoing
in
Quick question, Wangda. When you say that the feature can be turned
off, do you mean resource types or resource profiles? I know there's an
off-by-default property that governs resource profiles, but I didn't see
any way to turn off resource types. Even if only CPU and memory are
Really looking forward to getting this in.
Couple of questions:
* Can you maybe comment a bit on the type of scale testing done ?
Specifically, the number of resources tested with and any point where it is
discovered that performance might take a hit. Also, given that we do not
have AM's that
Thank you very much Varun Vasudev, Wangda Tan, Daniel and all the folks who
helped in getting this feature in this level.
Starting with my +1 (binding).
# Tested a 5 node cluster with resource profiles enabled/disabled (feature
is disabled by default)
# All apis added are marked as
Hi folks,
Per earlier discussion [1], I'd like to start a formal vote to merge
feature branch YARN-3926 (Resource profile) to trunk. The vote will run for
7 days and will end August 30 10:00 AM PDT.
Briefly, YARN-3926 can extend resource model of YARN to support resource
types other than CPU