ritize this. Hoping to get to this next
>> week.
>>
>> Jonathan
>>
>> --
>> *From:* Jim Brennan
>> *Sent:* Thursday, April 18, 2019 7:28 AM
>> *To:* Jonathan Hung
>> *Cc:* yarn-...@hadoop.apache.org; mapreduce-dev@hadoop.
..@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
> *Subject:* Re: [DISCUSS] Merging YARN-8200 to branch-3.0 and branch-2
>
> Hi Jonathan,
>
> Hi Jim, we have not tested rolling upgrade. I don’t foresee this being an
>> issue, but we’ll try it out and report back.
>
>
<mailto:yarn-...@hadoop.apache.org>;
mapreduce-dev@hadoop.apache.org<mailto:mapreduce-dev@hadoop.apache.org>
Subject: Re: [DISCUSS] Merging YARN-8200 to branch-3.0 and branch-2
Thanks for working on this!
One concern for us is support for a rolling upgrade. If we are running a
clu
ing an
> issue, but we’ll try it out and report back.
>
> Jonathan
>
> --
> *From:* Jim Brennan
> *Sent:* Tuesday, April 2, 2019 9:17 AM
> *To:* Jonathan Hung
> *Cc:* yarn-...@hadoop.apache.org; mapreduce-dev@hadoop.apache.org
> *Subject:* Re: [
@hadoop.apache.org
Subject: Re: [DISCUSS] Merging YARN-8200 to branch-3.0 and branch-2
Thanks for working on this!
One concern for us is support for a rolling upgrade. If we are running a
cluster based on branch-2.8, will we be able to do a rolling upgrade (no
cluster down-time) to a branch containing these
Thanks for working on this!
One concern for us is support for a rolling upgrade. If we are running a
cluster based on branch-2.8, will we be able to do a rolling upgrade (no
cluster down-time) to a branch containing these changes? Have you tested
rolling upgrades?
Thanks.
Jim
On Fri, Mar 29, 20
Sounds like a good idea to me.
This has been tested on branch-2 in production for some time and benchmarks
look good.
Thanks,
--Konstantin
On Fri, Mar 29, 2019 at 12:14 PM Jonathan Hung wrote:
> Hello devs,
>
> Starting a discuss thread to merge resource types/native GPU scheduling
> support to
Hello devs,
Starting a discuss thread to merge resource types/native GPU scheduling
support to branch-3.0 and branch-2. The resource types work was done in
trunk~branch-3.0 and GPU support done in trunk~branch-3.1, so the proposal
is to merge GPU support into branch-3.0 and both resource types/GPU