Re: Store Large files on HBase/HDFS
maybe U can parse the HDFS image file, then transform them as the Hfile, and load into hbase Tables. --remember to partition the hbase table 2016-02-18 7:40 GMT+08:00 Arun Patel <arunp.bigd...@gmail.com>: > I would like to store large documents (over 100 MB) on HDFS and insert > metadata in HBase. > > 1) Users will use HBase REST API for PUT and GET requests for storing and > retrieving documents. In this case, how to PUT and GET documents to/from > HDFS?What are the recommended ways for storing and accessing document > to/from HDFS that provides optimum performance? > > Can you please share any sample code? or a Github project? > > 2) What are the performance issues I need to know? > > Regards, > Arun > -- Thanks & Regards, 李剑 Jameson Li Focus on Hadoop,Mysql
Re: HBase atomic update
it seems parallel-update issue for the same rowkey and column? can you let the column with multi-versions and every update using a special timestamp, ti will be work and bypass the parallel-update issue. And when just two parallel request update same-rowkey-same-column-same-timestamp, there isn't impossibility way to solve it, it will let a random query success and another fail or retry. If just need this cases, and not want random solves, Or maybe there is some other way to let the parallel request have an ordered order, rather than parallel in an same nanosecond. 2016-01-26 4:40 GMT+08:00 Yakubovich, Alexey <alexey.yakubov...@searshc.com> : > I am trying to master HBase, and vuala, I discover that so nice API > components: > > checkAndPut, checkAndDelete, Increment, Append (HTable) > > Or may be not so nice? So e.g. checkAndPut can atomically update the > specified cell. > But what if I want to update two cells (from one row) in one atomic > operation? What if it’s two cells from two different rows, but in need to > be updated atomically? > > What is the best way to achieve that? > > Thank you > Alexey > > This message, including any attachments, is the property of Sears Holdings > Corporation and/or one of its subsidiaries. It is confidential and may > contain proprietary or legally privileged information. If you are not the > intended recipient, please delete it without reading the contents. Thank > you. > -- Thanks & Regards, 李剑 Jameson Li Focus on Hadoop,Mysql
Re: parallel scanning?
2016-01-26 2:29 GMT+08:00 Henning Blohm <henning.bl...@zfabrik.de>: > I am looking for advise on an HBase mass data access optimization problem. > For multi-get and multi-scan: In my opion, multi-get(make less line) can work in realtime query, but multi-scan maybe work but it will let server busy easy and effect other small-query to a big query time. But multi-get's query time will not stable, when one of the region is busy the whole time will up. For realtime and offline: watch your real query result, when the result line is so much lines, like Mbyte or 10Mbyte, it's quert time will not so good as miliseconds, because of the network trans time. We must reduce the result lines or result sizes or result columns. or it is not suit the real-realtime query. if actually need so much querys and so much big-szie results, suggest to work with offline and parallel, but not realtime, because also the server network-through will not work(1000M BIT NIC for 2M byte/qps, a server just handler 50qps). if just the query issue(multi-scan and multi-get), I think we can waste store to up the query performance, just using an extra table(maybe will write twice) and using another schema, eg: one table with rowkey as A_B_time, another as B_A_time, when query B%, we just query table rowkey B_A_time that just one small-scan, and not need for query table row A_B_time with multi_scans. Hope helpful for U. -- Thanks & Regards, 李剑 Jameson Li Focus on Hadoop,Mysql
Re: Fuzzy Row filter with ranges
2016-02-01 19:08 GMT+08:00 Jean-Marc Spaggiari <jean-m...@spaggiari.org>:
> example of what you are trying to d
like query prefixKey%, you can struct a query like this
startRow=Bytes.toBytes(prefixKey) ，
stopRow=Bytes.add(prefixKey, new byte[]{(byte)0xff})
And be remember set setCacheBlocks(false), if the query will not query
repeat.
And remember let a certain start and end, even if as a PrefixScan(sometimes
just write start but not end, it maybe scan the whole bottom half of the
table), and let the section smaller with query more faster.
--
Thanks & Regards,
李剑 Jameson Li
Focus on Hadoop,Mysql
Re: parallel scanning?
''By line, did you mean number of rows ? Yes, sorry for my poor English. ''In the above case, handling failed write (to the second table) becomes a bit tricky. Yes, But I think sometimes write question will can solve easier than read, and that sometimes we can write twice/multi-time with no problem(premise do not operate column timestamp) 2016-02-05 20:13 GMT+08:00 Ted Yu <yuzhih...@gmail.com>: > bq. when the result line is so much lines > > By line, did you mean number of rows ? > > bq. one table with rowkey as A_B_time, another as B_A_time > > In the above case, handling failed write (to the second table) becomes a > bit tricky. > > Cheers > > On Fri, Feb 5, 2016 at 12:08 AM, Jameson Li <hovlj...@gmail.com> wrote: > > > 2016-01-26 2:29 GMT+08:00 Henning Blohm <henning.bl...@zfabrik.de>: > > > > > I am looking for advise on an HBase mass data access optimization > > problem. > > > > > > > For multi-get and multi-scan: > > In my opion, multi-get(make less line) can work in realtime query, but > > multi-scan maybe work but it will let server busy easy and effect other > > small-query to a big query time. > > But multi-get's query time will not stable, when one of the region is > busy > > the whole time will up. > > > > For realtime and offline: > > watch your real query result, when the result line is so much lines, like > > Mbyte or 10Mbyte, it's quert time will not so good as miliseconds, > because > > of the network trans time. We must reduce the result lines or result > sizes > > or result columns. or it is not suit the real-realtime query. > > if actually need so much querys and so much big-szie results, suggest to > > work with offline and parallel, but not realtime, because also the server > > network-through will not work(1000M BIT NIC for 2M byte/qps, a server > just > > handler 50qps). > > > > if just the query issue(multi-scan and multi-get), I think we can waste > > store to up the query performance, just using an extra table(maybe will > > write twice) and using another schema, eg: one table with rowkey as > > A_B_time, another as B_A_time, when query B%, we just query table rowkey > > B_A_time that just one small-scan, and not need for query table row > > A_B_time with multi_scans. > > > > Hope helpful for U. > > > > > > > > > > -- > > > > > > Thanks & Regards, > > 李剑 Jameson Li > > Focus on Hadoop,Mysql > > > -- Thanks & Regards, 李剑 Jameson Li Focus on Hadoop,Mysql
Re: Fuzzy Row filter with ranges
2016-02-05 23:25 GMT+08:00 Jean-Marc Spaggiari <jean-m...@spaggiari.org>: > Consider Yes, You are right. We should consider the real range for the rowkey, just a thinking way to struct the start and end, I am sorry somebody misguided by me. -- Thanks & Regards, 李剑 Jameson Li Focus on Hadoop,Mysql
Re: upgrade hbase from 0.20.6 to 0.92
2012/2/21 Stack st...@duboce.net As I know, zookeeper 3.4.2 is not a stable version. Where is that written? The website http://zookeeper.apache.org/releases.html said: About zookeeper 3.4.3, it is a beta release. And about zookeeper 3.4.2, it is an alpha release.
Re: upgrade hbase from 0.20.6 to 0.92
Thanks very much. And I have another question. The hbase books said: If you can, upgrade your zookeeper. If you can’t, 3.4.2 clients should work against 3.3.X ensembles (HBase makes use of 3.4.2 API). As I know, zookeeper 3.4.2 is not a stable version. So I can't upgrade hbase cluster to version 0.92? Can hbase 0.92 and zookeeper 3.3 work well? Jameson Li. 2012/2/17 Stack st...@duboce.net On Thu, Feb 16, 2012 at 11:13 PM, Jameson Li hovlj...@gmail.com wrote: Follow the 0.90 upgrade steps first. Verify its working properly up on 0.90. Then go to 0.92. Don't try replacing pieces of the tar ball piecemeal. Use all of 0.90 (but yes, adjust the confs accordingly). I am sorry that my English is weak poorly and I can't understand: Don't try replacing pieces of the tar ball piecemeal. Use all of 0.90 (but yes, adjust the confs accordingly) Do you mean: when I do the 0.92 upgrade, I should use the same way updating 0.90? Just like you mentioned that: You need to replace your whole install, not just the jar (different dependencies, supporting scripts have changed, etc.) Yes. St.Ack
upgrade hbase from 0.20.6 to 0.92
Hi, *I want to upgrade our hbase cluster from version 0.20.6 to 0.92, but the hbase book just tell me how to upgrade from version 0.90 to 0.92.* *So I have a doubt that: * *Can I directly upgrade? Or I have to firstly upgrade it to 0.90 version, then upgrade it from verion 0.90 to 0.92.* * * *And 0.20.6 to 0.90, just replace the jar file and run:* *hbase org.jruby.Main $HBASE_HOME/bin/set_meta_memstore_size.rb* * * *And 0.90 to 0.92, just change the zookeeper version to 3.4.2 and take care the below confs:* *-- base.hregion.memstore.mslab.enabled* *-- adds distributed WAL log splitting in place of single-process master orchestrated splitting(default on)* *-- hbase.instant.schema.alter.enabled* *-- off-heap cache* *-- regionserver OOM kill -9* * * *Does there have steps that I omit?* * * *Thanks,* *Jameson Li.*
Re: hbase host dns ip and route for multi network interface card
Hbase version:0.20.6 Hadoop version:0.20-append+4 Zookeeper version:3.3.0 2011/7/8 Stack st...@duboce.net Is this 0.20.x hbase? You should upgrade. See in below. On Fri, Jul 8, 2011 at 4:15 AM, Jameson Li hovlj...@gmail.com wrote: resolve to 192.168.1.13 logs org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed setting up proxy to /192.168.1.13:60020 after attempts=1 Its not finding a name to match 192.168.1.13? 2011-07-05 17:14:14,313 DEBUG org.apache.hadoop.hbase.master.BaseScanner: Current assignment of .META.,,1 is not valid; serverAddress= 192.168.1.13:60020, startCode=1309857199677 unknown. Yeah, you need to fix the naming to make the above work. org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed setting up proxy to /192.168.1.13:60020 after attempts=1 This looks like reverse lookup does not agree with forward lookup. Have you checked that? The regionserver is saying its 1.13 but master doesn't know who that is. St.Ack
Re: hbase host dns ip and route for multi network interface card
org.apache.hadoop.hbase.master.RegionServerOperation: Adding to
onlineMetaRegions: {server: 192.168.3.227:60020, regionname: .META.,,1,
startKey: }
2011-07-05 17:14:14,380 INFO org.apache.hadoop.hbase.master.BaseScanner:
RegionManager.metaScanner scanning meta region {server: 192.168.3.227:60020,
regionname: .META.,,1, startKey: }
2011-07-05 17:14:14,398 DEBUG org.apache.hadoop.hbase.master.BaseScanner:
Current assignment of LogC,,1301710464511 is not valid; serverAddress=
192.168.1.88:60020, startCode=1307417175471 unknown.
2011-07-05 17:14:14,403 DEBUG org.apache.hadoop.hbase.master.BaseScanner:
Current assignment of LogGifT,,1301479329059 is not valid; serverAddress=
192.168.1.88:60020, startCode=1307417175471 unknown.
2011-07-05 17:14:14,409 DEBUG org.apache.hadoop.hbase.master.BaseScanner:
Current assignment of StagingURLTag,,1293435609189 is not valid;
serverAddress=192.168.1.27:60020, startCode=1307417175541 unknown.
2011-07-05 17:14:14,413 INFO org.apache.hadoop.hbase.master.BaseScanner:
RegionManager.metaScanner scan of 3 row(s) of meta region {server:
192.168.3.227:60020, regionname: .META.,,1, startKey: } complete
2011-07-05 17:14:14,413 INFO org.apache.hadoop.hbase.master.BaseScanner: All
1 .META. region(s) scanned
2011/7/8 Stack st...@duboce.net
HBase just uses java resolver. You sure that when you do a resolve,
you don't get more than the one answer back on that machine?
St.Ack
On Thu, Jul 7, 2011 at 6:59 PM, Jameson Li hovlj...@gmail.com wrote:
All of the 5 nodes have the same /etc/hosts file, and the same line:
192.168.1.15 node3
I don't know why sometime hbase resolve the node3 to eth0 192.168.1.13.
Is there somewhere that is used to resolve the dns name:node3?
2011/7/7 Stack st...@duboce.net
Yeah, this is probably it. Can you make sure we resolve always to a
single address?
Re: hbase host dns ip and route for multi network interface card
All of the 5 nodes have the same /etc/hosts file, and the same line: 192.168.1.15 node3 I don't know why sometime hbase resolve the node3 to eth0 192.168.1.13. Is there somewhere that is used to resolve the dns name:node3? 2011/7/7 Stack st...@duboce.net Yeah, this is probably it. Can you make sure we resolve always to a single address?
hbase host dns ip and route for multi network interface card
Hi,
when I start my hbase cluster, there are some error logs in the master-log:
the ip and hostname node3 192.168.1.15 192.168.1.13 are the same machine
that have two NIC
2011-07-05 17:13:13,820 INFO org.apache.zookeeper.ClientCnxn:
zookeeper.disableAutoWatchReset is false
2011-07-05 17:13:13,840 INFO org.apache.zookeeper.ClientCnxn: Attempting
connection to server node3/192.168.1.15:2181
2011-07-05 17:13:13,975 DEBUG org.apache.hadoop.hbase.master.HMaster:
Checking cluster state...
2011-07-05 17:13:13,979 DEBUG
org.apache.hadoop.hbase.zookeeper.ZooKeeperWrapper: Read ZNode
/hbase/root-region-server got 192.168.1.13:60020
2011-07-05 17:13:19,732 DEBUG
org.apache.hadoop.hbase.zookeeper.ZooKeeperWrapper: Updated ZNode
/hbase/rs/1309857199677 with data 192.168.1.15:60020
2011-07-05 17:22:01,041 INFO org.apache.hadoop.ipc.HbaseRPC: Server at /
192.168.1.13:60020 could not be reached after 1 tries, giving up.
2011-07-05 17:22:01,042 WARN org.apache.hadoop.hbase.master.BaseScanner:
Scan one META region: {server: 192.168.1.13:60020, regionname: .META.,,1,
startKey: }org.apache.hadoop.hbase.client.RetriesExhaustedException:
Failed setting up proxy to /192.168.1.13:60020 after attempts=1
at
org.apache.hadoop.hbase.ipc.HBaseRPC.waitForProxy(HBaseRPC.java:429)
at
org.apache.hadoop.hbase.client.HConnectionManager$TableServers.getHRegionConnection(HConnectionManager.java:918)
at
org.apache.hadoop.hbase.client.HConnectionManager$TableServers.getHRegionConnection(HConnectionManager.java:934)
at
org.apache.hadoop.hbase.master.BaseScanner.scanRegion(BaseScanner.java:173)
at
org.apache.hadoop.hbase.master.MetaScanner.scanOneMetaRegion(MetaScanner.java:73)
at
org.apache.hadoop.hbase.master.MetaScanner.maintenanceScan(MetaScanner.java:129)
at
org.apache.hadoop.hbase.master.BaseScanner.chore(BaseScanner.java:153)
at org.apache.hadoop.hbase.Chore.run(Chore.java:68)
Sometimes when the .META. region is not assigned to the server node3, which
has two NIC:eth0:192.168.1.13 and eth1:192.168.1.15 and resolve the dns/host
as:192.168.1.15 node3, I means, when the region .META. is assigned to the
others server that has only one NIC, the hbase will work well.
here is some of my hbase cluster infos:
Hbase version:0.20.6
Hadoop version:0.20-append+4
Zookeeper version:3.3.0
the hbase-site.xml:
configuration
property
namehbase.rootdir/name
valuehdfs://node3:54310/hbase/value
/property
property
namehbase.master/name
valuehadoop5:6/value
/property
property
namehbase.zookeeper.quorum/name
valuenode3,hadoop5,hadoopoffice85,hadoopoffice88,hdofficelj001/value
/property
property
namehbase.cluster.distributed/name
valuetrue/value
/property
!--property
namehbase.master.dns.interface/name
valueeth1/value
descriptionThe name of the Network Interface from which a master
should report its IP address.
/description
/property
property
namehbase.regionserver.dns.interface/name
valueeth1/value
descriptionThe name of the Network Interface from which a region
server
should report its IP address.
/description
/property
property
namehbase.zookeeper.dns.interface/name
valueeth1/value
descriptionThe name of the Network Interface from which a ZooKeeper
server
should report its IP address.
/description
/property--
!--property
namehbase.zookeeper.property.clientPort/name
value/value
descriptionProperty from ZooKeeper's config zoo.cfg.
The port at which the clients will connect.
/description
/property
property
namehbase.zookeeper.property.dataDir/name
value/opt/zookeeper/data/value
descriptionProperty from ZooKeeper's config zoo.cfg.
The directory where the snapshot is stored.
/description
/property--
/configuration
cat /opt/hbase/conf/regionservers
hadoop5
node3
hadoopoffice85
hadoopoffice88
hdofficelj001
---
And the below is the node3's info:
192.168.1.13's ifconfig info:
[root@node3 ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0C:29:23:2E:D3
inet addr:192.168.1.13 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe23:2ed3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1424620 errors:0 dropped:0 overruns:0 frame:0
TX packets:17897973 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:150231810 (143.2 MiB) TX bytes:2834085782 (2.6 GiB)
Base address:0x2000 Memory:d892-d894
eth1 Link encap:Ethernet HWaddr 00:0C:29:23:2E:DD
inet addr:192.168.1.15 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20c:29ff:fe23:2edd/64 Scope:Link
UP BROADCAST
Re: hbase host dns ip and route for multi network interface card
Hi,
I think The problem is that:
the /etc/hosts file is resolved the dns node3 to 192.168.1.15eth1, but the
hbase inner sometime uses the 192.168.1.13eth0.
When I use the command ifdown eth0 on node3 and use stop-hbase.sh, there
shows the message:
2011-07-06 10:25:50,683 DEBUG org.apache.hadoop.hbase.master.RegionManager:
telling meta scanner to stop
2011-07-06 10:25:50,683 DEBUG org.apache.hadoop.hbase.master.RegionManager:
meta and root scanners notified
2011-07-06 10:26:00,685 DEBUG org.apache.hadoop.hbase.master.RegionManager:
telling root scanner to stop
2011-07-06 10:26:00,685 DEBUG org.apache.hadoop.hbase.master.RegionManager:
telling meta scanner to stop
2011-07-06 10:26:00,685 DEBUG org.apache.hadoop.hbase.master.RegionManager:
meta and root scanners notified
2011-07-06 10:26:10,687 DEBUG org.apache.hadoop.hbase.master.RegionManager:
telling root scanner to stop
2011-07-06 10:26:10,687 DEBUG org.apache.hadoop.hbase.master.RegionManager:
telling meta scanner to stop
2011-07-06 10:26:10,687 DEBUG org.apache.hadoop.hbase.master.RegionManager:
meta and root scanners notified
2011-07-06 10:26:20,689 DEBUG org.apache.hadoop.hbase.master.RegionManager:
telling root scanner to stop
2011-07-06 10:26:20,689 DEBUG org.apache.hadoop.hbase.master.RegionManager:
telling meta scanner to stop
2011-07-06 10:26:20,689 DEBUG org.apache.hadoop.hbase.master.RegionManager:
meta and root scanners notified
2011-07-06 10:26:30,691 DEBUG org.apache.hadoop.hbase.master.RegionManager:
telling root scanner to stop
And when I ifup eth0 on node3, it will work well and stop the hbase
normal:
2011-07-06 10:28:47,139 INFO org.apache.hadoop.hbase.master.ServerManager:
Region server node3,60020,1309860160318 quiesced
2011-07-06 10:28:47,139 INFO org.apache.hadoop.hbase.master.ServerManager:
All user tables quiesced. Proceeding with shutdown
2011-07-06 10:28:47,139 DEBUG org.apache.hadoop.hbase.master.RegionManager:
telling root scanner to stop
2011-07-06 10:28:47,139 DEBUG org.apache.hadoop.hbase.master.RegionManager:
telling meta scanner to stop
2011-07-06 10:28:47,139 DEBUG org.apache.hadoop.hbase.master.RegionManager:
meta and root scanners notified
2011-07-06 10:28:47,338 INFO org.apache.hadoop.hbase.master.ServerManager:
Removing server's info node3,60020,1309860160318
2011-07-06 10:28:47,338 INFO org.apache.hadoop.hbase.master.ServerManager:
Region server node3,60020,1309860160318: MSG_REPORT_EXITING
2011-07-06 10:28:50,719 INFO org.apache.hadoop.hbase.master.HMaster:
Stopping infoServer
2011/7/5 Jameson Li hovlj...@gmail.com
Hi,
when I start my hbase cluster, there are some error logs in the master-log:
the ip and hostname node3 192.168.1.15 192.168.1.13 are the same machine
that have two NIC
2011-07-05 17:13:13,820 INFO org.apache.zookeeper.ClientCnxn:
zookeeper.disableAutoWatchReset is false
2011-07-05 17:13:13,840 INFO org.apache.zookeeper.ClientCnxn: Attempting
connection to server node3/192.168.1.15:2181
2011-07-05 17:13:13,975 DEBUG org.apache.hadoop.hbase.master.HMaster:
Checking cluster state...
2011-07-05 17:13:13,979 DEBUG
org.apache.hadoop.hbase.zookeeper.ZooKeeperWrapper: Read ZNode
/hbase/root-region-server got 192.168.1.13:60020
2011-07-05 17:13:19,732 DEBUG
org.apache.hadoop.hbase.zookeeper.ZooKeeperWrapper: Updated ZNode
/hbase/rs/1309857199677 with data 192.168.1.15:60020
2011-07-05 17:22:01,041 INFO org.apache.hadoop.ipc.HbaseRPC: Server at /
192.168.1.13:60020 could not be reached after 1 tries, giving up.
2011-07-05 17:22:01,042 WARN org.apache.hadoop.hbase.master.BaseScanner:
Scan one META region: {server: 192.168.1.13:60020, regionname: .META.,,1,
startKey: }org.apache.hadoop.hbase.client.RetriesExhaustedException:
Failed setting up proxy to /192.168.1.13:60020 after attempts=1
at
org.apache.hadoop.hbase.ipc.HBaseRPC.waitForProxy(HBaseRPC.java:429)
at
org.apache.hadoop.hbase.client.HConnectionManager$TableServers.getHRegionConnection(HConnectionManager.java:918)
at
org.apache.hadoop.hbase.client.HConnectionManager$TableServers.getHRegionConnection(HConnectionManager.java:934)
at
org.apache.hadoop.hbase.master.BaseScanner.scanRegion(BaseScanner.java:173)
at
org.apache.hadoop.hbase.master.MetaScanner.scanOneMetaRegion(MetaScanner.java:73)
at
org.apache.hadoop.hbase.master.MetaScanner.maintenanceScan(MetaScanner.java:129)
at
org.apache.hadoop.hbase.master.BaseScanner.chore(BaseScanner.java:153)
at org.apache.hadoop.hbase.Chore.run(Chore.java:68)
Sometimes when the .META. region is not assigned to the server node3, which
has two NIC:eth0:192.168.1.13 and eth1:192.168.1.15 and resolve the dns/host
as:192.168.1.15 node3, I means, when the region .META. is assigned to the
others server that has only one NIC, the hbase will work well.
here is some of my hbase cluster infos:
Hbase version:0.20.6
Hadoop version:0.20-append+4
Zookeeper version:3.3.0
the hbase-site.xml
table can't disable and scan
Hi,
Today I have added the lzo to the hadoop cluster, and also the
hbase(0.20.6).
Then I create a test table:
create 'mytable', {NAME='colfam:', COMPRESSION='lzo'}
It works fine.
And then I put a small test data, and other operation:
put 'mytable','key1','colfam:','value1'
scan 'mytable'
deleteall 'mytable','key1'
disable 'mytable'
drop 'mytable'
When I do one of the operation, I got the error message, and I can't modify
the table 'mytable':
NativeException: org.apache.hadoop.hbase.client.RetriesExhaustedException:
Trying to contact region server 192.168.11.111:60020 for region
mytable,,1302077037075, row '', but failed after 7 attempts.
Exceptions:
org.apache.hadoop.hbase.NotServingRegionException:
org.apache.hadoop.hbase.NotServingRegionException: mytable,,1302077037075
at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:2269)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.openScanner(HRegionServer.java:1848)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.hadoop.hbase.ipc.HBaseRPC$Server.call(HBaseRPC.java:657)
at
org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:915)
How can I recover this table 'mytable'?
Thanks,
Jameson Li.
Re: table can't disable and scan
Hi,
The table 'mytable' has only one region, and when I goto this regionserver,
I can't see any region name about the table 'mytable'.
When I want to disable this table and drop it, it shows:
hbase(main):058:0 disable 'mytable'
NativeException: org.apache.hadoop.hbase.RegionException: Retries exhausted,
it took too long to wait for the table mytable to be disabled.
And the logs log in the regionserver:
2011-04-07 10:35:44,640 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: MSG_REGION_CLOSE:
mytable,,1302077037075
2011-04-07 10:35:44,640 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Worker:
MSG_REGION_CLOSE: mytable,,1302077037075
2011-04-07 10:35:45,648 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: MSG_REGION_CLOSE:
mytable,,1302077037075
2011-04-07 10:35:45,648 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Worker:
MSG_REGION_CLOSE: mytable,,1302077037075
2011-04-07 10:35:46,655 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: MSG_REGION_CLOSE:
mytable,,1302077037075
2011-04-07 10:35:46,655 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Worker:
MSG_REGION_CLOSE: mytable,,1302077037075
2011-04-07 10:35:47,666 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: MSG_REGION_CLOSE:
mytable,,1302077037075
2011-04-07 10:35:47,666 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Worker:
MSG_REGION_CLOSE: mytable,,1302077037075
2011-04-07 10:35:49,685 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: MSG_REGION_CLOSE:
mytable,,1302077037075
2011-04-07 10:35:49,685 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Worker:
MSG_REGION_CLOSE: mytable,,1302077037075
2011-04-07 10:35:51,697 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: MSG_REGION_CLOSE:
mytable,,1302077037075
2011-04-07 10:35:51,697 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Worker:
MSG_REGION_CLOSE: mytable,,1302077037075
2011-04-07 10:35:55,727 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: MSG_REGION_CLOSE:
mytable,,1302077037075
2011-04-07 10:35:55,727 INFO
org.apache.hadoop.hbase.regionserver.HRegionServer: Worker:
MSG_REGION_CLOSE: mytable,,1302077037075
And also I have created/put/deleteall/disable/drop anohter table 'mytable1':
create 'mytable', {NAME='colfam:', COMPRESSION='lzo'}
Everything goes well.
But so strangely about the table 'mytable'.
Thanks,
Jameson Li.
2011/4/7 Stack st...@duboce.net
And, see http://hbase.apache.org/book.html#lzo
St.Ack
On Wed, Apr 6, 2011 at 9:56 AM, Jean-Daniel Cryans jdcry...@apache.org
wrote:
Check the region server log, you probably missed something when
configuring your table.
J-D
On Wed, Apr 6, 2011 at 2:15 AM, Jameson Li hovlj...@gmail.com wrote:
Hi,
Today I have added the lzo to the hadoop cluster, and also the
hbase(0.20.6).
Then I create a test table:
create 'mytable', {NAME='colfam:', COMPRESSION='lzo'}
It works fine.
And then I put a small test data, and other operation:
put 'mytable','key1','colfam:','value1'
scan 'mytable'
deleteall 'mytable','key1'
disable 'mytable'
drop 'mytable'
When I do one of the operation, I got the error message, and I can't
modify
the table 'mytable':
NativeException:
org.apache.hadoop.hbase.client.RetriesExhaustedException:
Trying to contact region server 192.168.11.111:60020 for region
mytable,,1302077037075, row '', but failed after 7 attempts.
Exceptions:
org.apache.hadoop.hbase.NotServingRegionException:
org.apache.hadoop.hbase.NotServingRegionException:
mytable,,1302077037075
at
org.apache.hadoop.hbase.regionserver.HRegionServer.getRegion(HRegionServer.java:2269)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.openScanner(HRegionServer.java:1848)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.hadoop.hbase.ipc.HBaseRPC$Server.call(HBaseRPC.java:657)
at
org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:915)
How can I recover this table 'mytable'?
Thanks,
Jameson Li.
