Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 20 Nov 2011 17:59:51 +0000 (UTC)
From: "Linden Hillenbrand (Updated) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <628835984.49161.1321811991847.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <832508669.49158.1321811871711.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HBASE-4834) CopyTable: Cannot have ZK source to
 destination
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Linden Hillenbrand updated HBASE-4834:
--------------------------------------

    Priority: Critical  (was: Major)
    
> CopyTable: Cannot have ZK source to destination
> -----------------------------------------------
>
>                 Key: HBASE-4834
>                 URL: https://issues.apache.org/jira/browse/HBASE-4834
>             Project: HBase
>          Issue Type: Bug
>          Components: zookeeper
>    Affects Versions: 0.90.1
>            Reporter: Linden Hillenbrand
>            Priority: Critical
>
> During a Copy Table, involving --peer.adr, we found the following block of code:
> if (address != null) {
>         ZKUtil.applyClusterKeyToConf(this.conf, address);
>    }
> When we set ZK conf in setConf method, that also gets called in frontend when MR initializes TOF, so there's no way now to have two ZK points for a single job, cause source gets reset before job is submitted.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira