You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Ajit Kumar (JIRA)" <ji...@apache.org> on 2016/04/20 23:37:25 UTC
[jira] [Created] (AMBARI-16001) Fix bad entry in hbase-env.sh that
were added as part of 2.2.0-2.2.1.1 upgrade
Ajit Kumar created AMBARI-16001:
-----------------------------------
Summary: Fix bad entry in hbase-env.sh that were added as part of 2.2.0-2.2.1.1 upgrade
Key: AMBARI-16001
URL: https://issues.apache.org/jira/browse/AMBARI-16001
Project: Ambari
Issue Type: Bug
Components: ambari-server
Affects Versions: 2.2.2
Reporter: Ajit Kumar
Assignee: Ajit Kumar
Fix For: 2.2.2
Ambari upgrades, 2.2.0-2.2.1.1 adds a bad entry to the hbase-env
{code}export HBASE_OPTS="-Djava.io.tmpdir={{java_io_tmpdir}}\""{code}
With broken hbase-env user cannot run any mapreduce services for hbase. Currently it needs to be fixed manually.
{code}
export HBASE_OPTS="${HBASE_OPTS} -Djava.io.tmpdir={{java_io_tmpdir}}"
{code}
It will be good if just upgrading to 2.2.2 fixes this issue rather than mucking around with configs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)