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

NN/RM charm should include a spark user/group

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 1.1.0
    • Fix Version/s: 1.2.0
    • Component/s: deployment
    • Labels:
      None

      Description

      When in 'yarn-client' mode, the spark charm creates a directory in hdfs with 'spark' user/group permissions.

      If spark is not colocated with the NN and RM, this user/group does not exist on those machines. This causes warnings in the hdfs log like this:

      WARN org.apache.hadoop.security.UserGroupInformation: No groups available for user spark

      It also prevents the RM history server from accessing spark job history files.

      To combat this, always include a spark user/group in the NN/RM charms. This is very similar to how we always create a 'mapred' user on the NN to prevent warnings about mapred being unknown to the namenode.

        Issue Links

          Activity

          Hide
          githubbot ASF GitHub Bot added a comment -

          GitHub user kwmonroe opened a pull request:

          https://github.com/apache/bigtop/pull/163

          BIGTOP-2603: NN/RM charm should include a spark user/group

          When NN/RM are not colocated with spark, they do not know about the spark user/group. When in `yarn-client` mode, the spark charm will create hdfs dirs with `spark` ACLs. This leads to errors like this on the namenode:

          `WARN org.apache.hadoop.security.UserGroupInformation: No groups available for user spark`

          Always create the spark user/group on NN and RM. This also works if spark/NN/RM are all colocated.

          Note that `hadoop` should be a secondary group (not primary) for extra users created by these charms, so this PR ensures that as well.

          You can merge this pull request into a Git repository by running:

          $ git pull https://github.com/juju-solutions/bigtop bug/BIGTOP-2603/add-spark-user

          Alternatively you can review and apply these changes as the patch at:

          https://github.com/apache/bigtop/pull/163.patch

          To close this pull request, make a commit to your master/trunk branch
          with (at least) the following in the commit message:

          This closes #163


          commit 74b427eccaafd0fd44f5d5aba2289d166388cdd3
          Author: Kevin W Monroe <kevin.monroe@canonical.com>
          Date: 2016-11-22T23:38:58Z

          add spark user/group so they always exist on NN and RM (prevents warnings when NN/RM are not colocated with spark)


          Show
          githubbot ASF GitHub Bot added a comment - GitHub user kwmonroe opened a pull request: https://github.com/apache/bigtop/pull/163 BIGTOP-2603 : NN/RM charm should include a spark user/group When NN/RM are not colocated with spark, they do not know about the spark user/group. When in `yarn-client` mode, the spark charm will create hdfs dirs with `spark` ACLs. This leads to errors like this on the namenode: `WARN org.apache.hadoop.security.UserGroupInformation: No groups available for user spark` Always create the spark user/group on NN and RM. This also works if spark/NN/RM are all colocated. Note that `hadoop` should be a secondary group (not primary) for extra users created by these charms, so this PR ensures that as well. You can merge this pull request into a Git repository by running: $ git pull https://github.com/juju-solutions/bigtop bug/ BIGTOP-2603 /add-spark-user Alternatively you can review and apply these changes as the patch at: https://github.com/apache/bigtop/pull/163.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #163 commit 74b427eccaafd0fd44f5d5aba2289d166388cdd3 Author: Kevin W Monroe <kevin.monroe@canonical.com> Date: 2016-11-22T23:38:58Z add spark user/group so they always exist on NN and RM (prevents warnings when NN/RM are not colocated with spark)
          Hide
          githubbot ASF GitHub Bot added a comment -

          Github user ktsakalozos commented on the issue:

          https://github.com/apache/bigtop/pull/163

          LGTM +1 . Do you think we should be doing the same with other components that may use hdfs, like hbase?

          Show
          githubbot ASF GitHub Bot added a comment - Github user ktsakalozos commented on the issue: https://github.com/apache/bigtop/pull/163 LGTM +1 . Do you think we should be doing the same with other components that may use hdfs, like hbase?
          Hide
          githubbot ASF GitHub Bot added a comment -

          Github user kwmonroe commented on the issue:

          https://github.com/apache/bigtop/pull/163

          Yeah, we probably should. `oozie` and `hue` come to mind. We chatted about this a little while ago. It would really be nice if the charm that relied on `hadoop-plugin` would send user info over the plugin relation.

          The plugin would then proxy that to the NN or RM as needed. Unfortunately, this isn't really a priority at the moment, so I think we'll treat `spark` as special for now and work up a more generic solution later.

          Show
          githubbot ASF GitHub Bot added a comment - Github user kwmonroe commented on the issue: https://github.com/apache/bigtop/pull/163 Yeah, we probably should. `oozie` and `hue` come to mind. We chatted about this a little while ago. It would really be nice if the charm that relied on `hadoop-plugin` would send user info over the plugin relation. The plugin would then proxy that to the NN or RM as needed. Unfortunately, this isn't really a priority at the moment, so I think we'll treat `spark` as special for now and work up a more generic solution later.
          Hide
          githubbot ASF GitHub Bot added a comment -

          Github user asfgit closed the pull request at:

          https://github.com/apache/bigtop/pull/163

          Show
          githubbot ASF GitHub Bot added a comment - Github user asfgit closed the pull request at: https://github.com/apache/bigtop/pull/163
          Hide
          kwmonroe Kevin W Monroe added a comment -
          Show
          kwmonroe Kevin W Monroe added a comment - Closing out. Charms with this fix are available at: https://jujucharms.com/hadoop-namenode/ https://jujucharms.com/hadoop-resourcemanager/

            People

            • Assignee:
              kwmonroe Kevin W Monroe
              Reporter:
              kwmonroe Kevin W Monroe
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development