hdp 2.0 jsvc_home incorrect

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.

Release Notes

None

Activity

Show:

Chris Gianelloni September 15, 2015 at 7:22 PM

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.

Derek Wood September 12, 2015 at 12:43 AM

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

Chris Gianelloni September 11, 2015 at 11:27 PM

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.

Chris Gianelloni September 11, 2015 at 11:25 PM

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...

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Components

Priority

Created September 11, 2015 at 11:14 PM
Updated September 15, 2015 at 7:45 PM
Resolved September 15, 2015 at 7:45 PM