ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajit Kumar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-16001) Fix bad entry in hbase-env.sh, added as part of 2.2.0-2.2.1.1 upgrade
Date Mon, 25 Apr 2016 19:04:12 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-16001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ajit Kumar updated AMBARI-16001:
--------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

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

Mime
View raw message