Uploaded image for project: 'Bigtop'
  1. Bigtop
  2. BIGTOP-1746

Introduce the concept of roles in bigtop cluster deployment

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.8.0
    • Fix Version/s: 1.1.0
    • Component/s: deployment
    • Labels:

      Description

      Currently, during cluster deployment, puppet categorizes nodes as head_node, worker_nodes, gateway_nodes, standy_node based on user specified info. This functionality gives user control over picking up a particular node as head_node, standy_node, gateway_node and rest others as worker_nodes. But, I woulld like to have more fine-grained control on which deamons should run on which node. For example, I do not want to run namenode, datanode on the same node. This functionality can be introduced with the concept of roles. Each node can be assigned a set of role. For example, Node A can be assigned ["namenode", "resourcemanager"] roles. Node B can be assigned ["datanode", "nodemanager"] and Node C can be assigned ["nodemanager", "hadoop-client"]. Now, each node will only run the specified daemons. Prerequisite for this kind of deployment is that each node should be given the necessary configurations that it needs to know. For example, each datanode should know which is the namenode etc... This functionality will allow users to customize the cluster deployment according to their needs.

        Attachments

        1. BIGTOP-1746.patch
          41 kB
          vishnu gajendran
        2. BIGTOP-1746.patch
          41 kB
          vishnu gajendran
        3. BIGTOP-1746.patch
          41 kB
          vishnu gajendran
        4. BIGTOP-1746.patch
          36 kB
          vishnu gajendran
        5. BIGTOP-1746.patch
          36 kB
          vishnu gajendran

          Issue Links

            Activity

              People

              • Assignee:
                vishnu vishnu gajendran
                Reporter:
                vishnu vishnu gajendran
              • Votes:
                0 Vote for this issue
                Watchers:
                12 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: