You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Linden Hillenbrand (Created) (JIRA)" <ji...@apache.org> on 2011/11/20 18:57:51 UTC
[jira] [Created] (HBASE-4834) CopyTable: Cannot have ZK source to
destination
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
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] [Resolved] (HBASE-4834) CopyTable: Cannot have ZK source to
destination
Posted by "Harsh J (Resolved) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-4834) CopyTable: Cannot have ZK source to
destination
Posted by "Harsh J (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-4834) CopyTable: Cannot have ZK source to
destination
Posted by "Linden Hillenbrand (Commented) (JIRA)" <ji...@apache.org>.
[ 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
Posted by "Linden Hillenbrand (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (HBASE-4834) CopyTable: Cannot have ZK source to
destination
Posted by "Linden Hillenbrand (Updated) (JIRA)" <ji...@apache.org>.
[ 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