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

Nick Dimiduk updated HBASE-4947:
--------------------------------

    Component/s: mapreduce
    
> CopyTable warns about being unable to find table from wrong instance of HBase
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-4947
>                 URL: https://issues.apache.org/jira/browse/HBASE-4947
>             Project: HBase
>          Issue Type: Bug
>          Components: mapreduce
>    Affects Versions: 0.90.4, 0.92.0
>            Reporter: Jonathan Hsieh
>            Priority: Minor
>
> Using CopyTable with two clusters, test01 and test02.
> cluster cluster01 has a table called 'table' which has a little bit of data 
> in it.
> cluster cluster02 has a table called 'table2' which have the same schema as 
> cluster01's 'table'
> Here's the command line used from a machine in cluster01
> {code}
> $ hbase org.apache.hadoop.hbase.mapreduce.CopyTable 
> --peer.adr=cluster02:2181:/hbase --new.name=table2 table
> {code}
> Job succeeds, but gives a scary extraneous warning:
> {code}
> 11/12/04 10:26:10 WARN client.HConnectionManager$HConnectionImplementation: 
> Encountered problems when prefetch META table:
> org.apache.hadoop.hbase.TableNotFoundException: Cannot find row in .META. for 
> table: table2, row=table2,,99999999999999
>         at 
> org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:136)
>         at 
> org.apache.hadoop.hbase.client.MetaScanner.metaScan(MetaScanner.java:95)
>         at 
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.prefetchRegionCache(HConnectionManager.java:649)
>         at 
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegionInMeta(HConnectionManager.java:703)
>         at 
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:594)
>         at 
> org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.locateRegion(HConnectionManager.java:559)
>         at org.apache.hadoop.hbase.client.HTable.<init>(HTable.java:173)
>         at org.apache.hadoop.hbase.client.HTable.<init>(HTable.java:147)
>         at 
> org.apache.hadoop.hbase.mapreduce.TableOutputFormat.setConf(TableOutputFormat.java:198)
>         at 
> org.apache.hadoop.util.ReflectionUtils.setConf(ReflectionUtils.java:62)
>         at 
> org.apache.hadoop.util.ReflectionUtils.newInstance(ReflectionUtils.java:117)
>         at org.apache.hadoop.mapred.JobClient$2.run(JobClient.java:869)
>         at org.apache.hadoop.mapred.JobClient$2.run(JobClient.java:833)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at javax.security.auth.Subject.doAs(Unknown Source)
>         at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1127)
>         at 
> org.apache.hadoop.mapred.JobClient.submitJobInternal(JobClient.java:833)
>         at org.apache.hadoop.mapreduce.Job.submit(Job.java:476)
>         at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:506)
>         at 
> org.apache.hadoop.hbase.mapreduce.CopyTable.main(CopyTable.java:201)
> 11/12/04 10:26:10 ERROR mapreduce.TableOutputFormat: 
> org.apache.hadoop.hbase.TableNotFoundException: table2
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to