[
https://issues.apache.org/jira/browse/HBASE-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153839#comment-13153839
]
Harsh J commented on HBASE-4834:
--------------------------------
Frontend calls setConf of TableOutputFormat when its initialized for
output-spec checks upon job.submit(), and that reloads the actual ZK keys in
job.xml itself (which, in Hadoop, is written _after_ checkOutputSpecs(…) and
such).
> 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
