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

Sandy Ryza commented on YARN-702:
---------------------------------

In the past couple weeks, I've had two different people come to me with 
problems related to this, one for HBase and one for Hue.  In both cases, they 
had put in a fair amount of research and were still not able to find a 
solution.  At the very least we should supply a lot more documentation.  But to 
me it seems like, if possible, I should be able to construct a job conf for a 
minicluster in exactly the same way I should for a regular cluster.  For a 
regular cluster, I do have to make sure the RM address is pointing to the right 
location, but I don't need to get the job conf from the cluster.  Putting this 
functionality in the NodeManager would also confer the advantage of saving the 
same work that was done in YARN-129 for non-MR frameworks.
                
> minicluster classpath construction requires user to set yarn.is.minicluster 
> in the job conf
> -------------------------------------------------------------------------------------------
>
>                 Key: YARN-702
>                 URL: https://issues.apache.org/jira/browse/YARN-702
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager
>    Affects Versions: 2.0.4-alpha
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>
> YARN-129 improved classpath construction for miniclusters by, when 
> yarn.is.minicluster is set, adding the current JVM's classpath to the 
> ContainerLaunchContext for the MR AM and tasks.  An issue with this is that 
> it requires the user to set yarn.is.minicluster on the mapreduce side in the 
> job conf, if they are not copying to RM conf into the jobconf.
> I think it would be better to bypass the ContainerLaunchContext and instead 
> have the nodemanager check the property, and if it is true, do the classpath 
> additions there.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to