Bigtop
  1. Bigtop
  2. BIGTOP-1211

Puppet recipes: Should they start a NodeManager if yarn is enabled?

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 0.7.0
    • Fix Version/s: None
    • Component/s: deployment
    • Labels:
      None

      Description

      Poking around in my vagrant-puppet deployer, im finding that I dont have a NM running.

      So I have to run:

       service hadoop-yarn-nodemanager start
      

      EVEN if i specify:

      components = yarn,hadoop 
      

      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?

        Activity

        jay vyas created issue -
        jay vyas made changes -
        Field Original Value New Value
        Description 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?
         
        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?
         
        Konstantin Boudnik made changes -
        Component/s Deployment [ 12316810 ]
        Konstantin Boudnik made changes -
        Affects Version/s 0.7.0 [ 12324362 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            jay vyas
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:

              Development