Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Component/s: hadoop
    • Labels:
      None
    • Rank:
      1|hzyznb:

      Description

      The JSVC_HOME in /etc/default/hadoop is incorrect on HDP 2.0 clusters (/usr/lib/bigtop-utils vs actual: /usr/libexec/bigtop-utils). This makes it impossible to spin up an HDP 2.0 cluster. We at least need to make it an attribute.

      History:
      https://github.com/caskdata/hadoop_cookbook/pull/135/files fixed it for HDP 2.[1,2], probably broke it for 2.0
      https://github.com/caskdata/hadoop_cookbook/pull/190/files hardcoded this change.

        Activity

        Hide
        Chris Gianelloni added a comment -

        It's not an attribute. The package only installs it into one place, so no need to make it configurable.

        You've verified that the directory is /usr/libexec/bigtop-utils on HDP 2.0 (which one?)... Let's check the rest. Also, this only affects secure clusters, which is probably how we missed this. Meh...

        Show
        Chris Gianelloni added a comment - It's not an attribute. The package only installs it into one place, so no need to make it configurable. You've verified that the directory is /usr/libexec/bigtop-utils on HDP 2.0 (which one?)... Let's check the rest. Also, this only affects secure clusters, which is probably how we missed this. Meh...
        Hide
        Chris Gianelloni added a comment -

        Also, can you verify where the jsvc binary comes from on that machine? What Linux distribution? I want to make sure that we're changing this correctly. I understood that it came from bigtop-jsvc in HDP-UTILS, which is the same no matter what version of HDP you use. The cookbook simply uses the same version of this repository for every HDP version.

        Show
        Chris Gianelloni added a comment - Also, can you verify where the jsvc binary comes from on that machine? What Linux distribution? I want to make sure that we're changing this correctly. I understood that it came from bigtop-jsvc in HDP-UTILS, which is the same no matter what version of HDP you use. The cookbook simply uses the same version of this repository for every HDP version.
        Hide
        Derek Wood added a comment -

        on centos6.6, HDP 2.0.13.0, which came with bigtop-jsvc-1.0.10:

        # rpm -ql bigtop-jsvc
        /usr/libexec/bigtop-utils
        /usr/libexec/bigtop-utils/jsvc
        /usr/share/doc/bigtop-jsvc-1.0.10
        /usr/share/doc/bigtop-jsvc-1.0.10/LICENSE.txt
        /usr/share/doc/bigtop-jsvc-1.0.10/NOTICE.txt
        /usr/share/doc/bigtop-jsvc-1.0.10/README
        /usr/share/doc/bigtop-jsvc-1.0.10/RELEASE-NOTES.txt
        
        Show
        Derek Wood added a comment - on centos6.6, HDP 2.0.13.0, which came with bigtop-jsvc-1.0.10: # rpm -ql bigtop-jsvc /usr/libexec/bigtop-utils /usr/libexec/bigtop-utils/jsvc /usr/share/doc/bigtop-jsvc-1.0.10 /usr/share/doc/bigtop-jsvc-1.0.10/LICENSE.txt /usr/share/doc/bigtop-jsvc-1.0.10/NOTICE.txt /usr/share/doc/bigtop-jsvc-1.0.10/README /usr/share/doc/bigtop-jsvc-1.0.10/RELEASE-NOTES.txt
        Hide
        Chris Gianelloni added a comment -

        Apparently, this package comes from the main HDP repositories, not HDP-UTILS, hence my confusion.

        https://github.com/caskdata/hadoop_cookbook/pull/221 is a fix.

        Show
        Chris Gianelloni added a comment - Apparently, this package comes from the main HDP repositories, not HDP-UTILS, hence my confusion. https://github.com/caskdata/hadoop_cookbook/pull/221 is a fix.

          People

          • Assignee:
            Chris Gianelloni
            Reporter:
            Derek Wood
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: