[
https://issues.apache.org/jira/browse/YARN-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449312#comment-16449312
]
Wangda Tan commented on YARN-8200:
----------------------------------
[~chris.douglas], I think [~sunilg] has already pointed out, the multiple
resource type backport could be very tricky. IIRC, [~templedf] spent lots of
time to backport from trunk to branch-3.0 in the last year and several issues
caused by backport. And now it diverges more, we have more changes (about 5+
months) added to trunk including many scheduler related changes.
[~shv], I understand you want a bridge release. I'm still +1 to have a 2.x
bridge release and backporting GPU related changes to branch-2. But it might be
worthwhile to look at 3.x release and fix migration issues so all users who
want to migrate to 3.x can benefit from such efforts. Just my $0.02.
> Backport resource types/GPU features to branch-2
> ------------------------------------------------
>
> Key: YARN-8200
> URL: https://issues.apache.org/jira/browse/YARN-8200
> Project: Hadoop YARN
> Issue Type: Task
> Reporter: Jonathan Hung
> Assignee: Jonathan Hung
> Priority: Major
>
> Currently we have a need for GPU scheduling on our YARN clusters to support
> deep learning workloads. However, our main production clusters are running
> older versions of branch-2 (2.7 in our case). To prevent supporting too many
> very different hadoop versions across multiple clusters, we would like to
> backport the resource types/resource profiles feature to branch-2, as well as
> the GPU specific support.
>
> We have done a trial backport of YARN-3926 and some miscellaneous patches in
> YARN-7069 based on issues we uncovered, and the backport was fairly smooth.
> We also did a trial backport of most of YARN-6223 (sans docker support).
>
> Regarding the backports, perhaps we can do the development in a feature
> branch and then merge to branch-2 when ready.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
