6 sec isn't crazy with 0.19. If you really want to research it, have a
look at where the time is spent, creating scanner or actually doing
the scanning. I think it's the former. That being said, upgrading to
0.20 is a much quicker solution. Scanner has been optimized in the new
version.
On Mon,
rpc
call fails at HConnectionManager.java locateRegionInMeta(...)
server.getClosestRowBefore(...) returning null with perfect legitimate
regionname and metakey.
solved by completely recreating hbase directory in hdfs.
Xinan
On Fri, May 29, 2009 at 7:11 PM, Xinan Wu wuxi...@gmail.com wrote:
Hi
pages/logs show all regions are ready but I
can't pull any data out from them.
On Sat, May 30, 2009 at 7:48 AM, stack st...@duboce.net wrote:
Tell us more about your cluster setup.
You've upped your file descriptors as per 'Getting Started' doc?
St.Ack
On Fri, May 29, 2009 at 7:11 PM, Xinan
don't see any obvious problems. you sure you changed conf correctly so
you are running indexed region server? you sure you insert values into
entry:hostname and entry:msg columns?
On Fri, May 29, 2009 at 1:24 AM, Rakhi Khatwani
rakhi.khatw...@gmail.com wrote:
Hi,
I was trying to create
Hi,
I started to experiment hbase-0.20 trunk code today and imported about
6GB data using native JAVA API. I occationally get
RetriesExhaustedException exception during importing and it's usually
fixable by restarting everything and resume importing from where it
stopped last time. But now I am
Hi,
I've been experimenting row scanning in hbase recently, following
advice from
http://devblog.streamy.com/2009/04/23/hbase-row-key-design-for-paging-limit-offset-queries/?.
One thing I notice is htable.getScanner() function call is very slow...
My table schema is very simple. Integer (as
. HBase 0.20 aims to fix this
substantially. Shocking speed gains are hopefully going to be par for the
course.
-ryan
On Thu, May 28, 2009 at 6:47 PM, Xinan Wu wuxi...@gmail.com wrote:
Hi,
I've been experimenting row scanning in hbase recently, following
advice from
http
