Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 6 Sep 2012 03:33:08 +1100 (NCT)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <653559604.39520.1346862788957.JavaMail.jiratomcat@arcas>
In-Reply-To: <2104391954.65082.1340849443921.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Updated] (HBASE-6288) In hbase-daemons.sh, description of
 the default backup-master file path is wrong
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lars Hofhansl updated HBASE-6288:
---------------------------------

    Fix Version/s: 0.96.0
    
> In hbase-daemons.sh, description of the default backup-master file path is wrong
> --------------------------------------------------------------------------------
>
>                 Key: HBASE-6288
>                 URL: https://issues.apache.org/jira/browse/HBASE-6288
>             Project: HBase
>          Issue Type: Task
>          Components: master, scripts, shell
>    Affects Versions: 0.92.0, 0.92.1, 0.94.0
>            Reporter: Benjamin Kim
>             Fix For: 0.96.0, 0.92.3, 0.94.2
>
>         Attachments: HBASE-6288-92-1.patch, HBASE-6288-92.patch, HBASE-6288-94.patch, HBASE-6288-trunk.patch
>
>
> In hbase-daemons.sh, description of the default backup-master file path is wrong
> {code}
> #   HBASE_BACKUP_MASTERS File naming remote hosts.
> #     Default is ${HADOOP_CONF_DIR}/backup-masters
> {code}
> it says the default backup-masters file path is at a hadoop-conf-dir, but shouldn't this be HBASE_CONF_DIR?
> also adding following lines to conf/hbase-env.sh would be helpful
> {code}
> # File naming hosts on which backup HMaster will run.  $HBASE_HOME/conf/backup-masters by default.
> export HBASE_BACKUP_MASTERS=${HBASE_HOME}/conf/backup-masters
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira