Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-21769

zeppelin principal and livy.superusers property do not match on upgraded cluster from Ambari 2.4.2 -and HDP 2.5.5

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.4.2
    • Fix Version/s: 2.5.2
    • Component/s: ambari-server
    • Labels:
      None

      Description

      In a cluster where the Spark and/or Spark2 Livy servers and Zeppelin are installed and Kerberos is enabled, it is expected that that livy-conf/livy.superusers and livy2-conf/livy.superusers contain the principal name of the Zeppelin user. However, this value is not always set, depending on the order in which the services were installed, when Kerberos was enabled, and whether an Ambari or stack upgrade was involved. And if it is set, the value may be incorrect since the Kerberos descriptor assumes the Zeppelin principal is zeppelin-<clustername>

      The solution is to move the logic to set the livy-conf/livy.superusers and livy2-conf/livy.superusers to the stack advisor to the appropriate value can be added as needed. Also while upgrading to Ambari 2.5.2, the value(s) should be fixed if necessary.

        Attachments

        1. AMBARI-21769_trunk_01.patch
          65 kB
          Robert Levas
        2. AMBARI-21769_branch-2.6_01.patch
          49 kB
          Robert Levas
        3. AMBARI-21769_branch-2.5_01.patch
          49 kB
          Robert Levas

          Issue Links

            Activity

              People

              • Assignee:
                rlevas Robert Levas
                Reporter:
                rlevas Robert Levas
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: