hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Brennan <james.bren...@verizonmedia.com.INVALID>
Subject Re: [DISCUSS] Merging YARN-8200 to branch-3.0 and branch-2
Date Tue, 02 Apr 2019 16:17:27 GMT
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?


On Fri, Mar 29, 2019 at 2:14 PM Jonathan Hung <jyhung2357@gmail.com> wrote:

> 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 support
> to branch-2.
> Internally we've been running resource types/GPU support off a fork of
> branch-2.9.0 in a > 300 node GPU cluster for a few months which has worked
> well. Also for completeness we verified that everything going into branch-2
> also exists in branch-3.0.
> The specific list of patches to merge is in feature branch
> YARN-8200.branch3 (for branch-3.0) and feature branch YARN-8200 (for
> branch-2). Full patches containing the YARN-8200.branch3 -> branch-3.0 diff
> and YARN-8200 -> branch-2 diff have been posted to YARN-8200 jira.
> If there's no issues from the community I'll start a merge vote next week.
> Thanks.
> Jonathan Hung

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message