You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "jay vyas (JIRA)" <ji...@apache.org> on 2014/02/16 03:11:19 UTC

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

jay vyas created BIGTOP-1211:
--------------------------------

             Summary: 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.  

{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)