[jira] [Commented] (BIGTOP-1211) Puppet recipes: Should they start a NodeManager if yarn is enabled?

["Konstantin Boudnik (JIRA)" <ji...@apache.org>]

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

Konstantin Boudnik commented on BIGTOP-1211:
--------------------------------------------

My understanding is that NM is being started by the recipe, but there was an issue with files system's folders permissions or something that prevented it from starting properly, IIRC.

> Puppet recipes:  Should they start a NodeManager if yarn is enabled?
> --------------------------------------------------------------------
>
>                 Key: BIGTOP-1211
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1211
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: jay vyas
>
> Poking around in my vagrant-puppet deployer, im finding that I dont have a NM running.  
> So I have to run:
> {noformat}
>  service hadoop-yarn-nodemanager start
> {noformat}
> EVEN if i specify:
> {noformat}
> components = yarn,hadoop 
> {noformat}
> So either: 
> 1) The nodemanager service should be a valid component that we can turn on or off in the config/site.csv file or
> 2) The puppet recipes should be smart enough to start a nodemanager for us (i.e. if yarn is a component than always start and run nodemanager). 
> I think (1) is better since in some deployments we may not want a NM on every node.
> Forgive me if this "bug" report is really not a bug at all, maybe just my ignorance on the way we are supposed to run NMs?
>  



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)