[jira] [Commented] (HBASE-4834) CopyTable: Cannot have ZK source to destination
[
https://issues.apache.org/jira/browse/HBASE-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153837#comment-13153837
]
Linden Hillenbrand commented on HBASE-4834:
---
Going to move to Table.Format.GetRecordWriter so that it is called. Moving
entire block in setconf in TableOutputFormat.java.
Harsh to test out locally, I will submit patch shortly.
> 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
[jira] [Commented] (HBASE-4834) CopyTable: Cannot have ZK source to destination
[
https://issues.apache.org/jira/browse/HBASE-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153845#comment-13153845
]
Linden Hillenbrand commented on HBASE-4834:
---
No worries, at least it was fixed and someone beat us to it. Thanks for your
help on the investigation 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
