[
https://issues.apache.org/jira/browse/AMBARI-16001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15252608#comment-15252608
]
Hudson commented on AMBARI-16001:
---------------------------------
SUCCESS: Integrated in Ambari-branch-2.2 #658 (See
[https://builds.apache.org/job/Ambari-branch-2.2/658/])
AMBARI-16001. Fix bad entry in hbase-env.sh, added as part of (ajit:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=fd3e212b414c59edeb49a982b8a4b6ebf92c6069])
*
ambari-server/src/test/java/org/apache/ambari/server/upgrade/UpgradeCatalog222Test.java
*
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog222.java
> Fix bad entry in hbase-env.sh, 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
>
> Attachments: rb45592.patch
>
>
> 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)
