You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2015/02/24 00:55:17 UTC
[jira] [Updated] (MESOS-2390) HADOOP_HOME no longer works with
fetcher
[ https://issues.apache.org/jira/browse/MESOS-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam B updated MESOS-2390:
--------------------------
Sprint: Mesosphere Q1 Sprint 4 - 3/6
Target Version/s: 0.22.0
Affects Version/s: 0.22.0
Shepherd: Adam B
Labels: fetcher hadoop hdfs mesosphere (was: fetcher hadoop hdfs)
> HADOOP_HOME no longer works with fetcher
> ----------------------------------------
>
> Key: MESOS-2390
> URL: https://issues.apache.org/jira/browse/MESOS-2390
> Project: Mesos
> Issue Type: Bug
> Components: fetcher, hadoop
> Affects Versions: 0.22.0
> Reporter: Adam B
> Assignee: Bernd Mathiske
> Labels: fetcher, hadoop, hdfs, mesosphere
>
> As of commit "699e638ef80739203ed38ba7238bbc176b107355 Consolidate all fetcher env vars into one that holds a JSON object." the HADOOP_HOME environment variable is no longer set when starting the fetcher, which means that hdfs.hpp's HDFS() will no longer look for the hadoop binary inside the user-provided HADOOP_HOME, whether it was specified via --hadoop_home or the HADOOP_HOME env variable.
> This is a regression in functionality from Mesos 0.21 and before, and breaks the use of HDFS when not installed in the slave's PATH. The future fetcher patch(es) for 0.23+ fixes this, but we need something in 0.22 to prevent regression.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)