[ 
https://issues.apache.org/jira/browse/YARN-8200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450136#comment-16450136
 ] 

Daniel Templeton edited comment on YARN-8200 at 4/24/18 4:05 PM:
-----------------------------------------------------------------

The challenge in backporting resource types into 3.0 was mostly just in 
splitting resource types from resource profiles.  Otherwise it wasn't bad.  But 
that was pull from 3.x into 3.0.  Going back into 2.x will be much trickier.  
The code that resource types touches is code that you want to handle very, very 
carefully because it's at the core of what the resource manager does.

I don't think it's a good idea to pull resource types back into 2.x.  Resource 
types represent a major change to the way the resource manager functions.  It's 
not something that appropriate for a minor release.  In fact, I would argue 
that resource types is one of the scarier changes in 3.0, so if you're willing 
to take on that risk in 2.x, you're probably better served just moving to 3.0.


was (Author: templedf):
The challenge in backporting resource types into 3.0 was mostly just in 
splitting resource types from resource profiles.  Otherwise it wasn't bad.  But 
that was pull from 3.x into 3.0.  Going back into 2.x will be much trickier.  
The code that resource types touches is code that you want to handle very, very 
carefully because it's at the core of what the resource manager does.

I don't think it's a good idea to pull resource types back into 2.x  Resource 
types represent a major change to the way the resource manager functions.  It's 
not something that appropriate for a minor release.  In fact, I would argue 
that resource types is one of the scarier changes in 3.0, so if you're willing 
to take on that risk in 2.x, you're probably better served just moving to 3.0.

> 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

Reply via email to