[ https://issues.apache.org/jira/browse/HBASE-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J resolved HBASE-4834. ---------------------------- Resolution: Duplicate This was fixed by HBASE-3497. Resolving as dup. Apologies for the noise, and for the confusion Linden! Regards, Harsh > 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