I'm sorry, but are you trying to say that you have multiple scanners trying to
read from a single region and the result sets do not match?
I guess it would be an easy test, enter a bunch of rows in to a region and have
a unique integer for each row. (1,2,3,...)
Then run a bunch of unfiltered scans in parallel, and generate a sum from the
scan. If any of the sums do not match, then you have a potential issue on
concurency/row locking, and row isolation level. How does HBase handle row
level locking and isolation levels?
-Mike
> Date: Thu, 22 Apr 2010 17:07:47 +0800
> Subject: multiple scanners on same table will cause problem? Scan results
> change among different tries.
> From: steven.zhuang.1...@gmail.com
> To: hbase-user@hadoop.apache.org
>
> hi, All,
> Has anybody do scan on one table using multiple scanners at the
> same time and found some inconsistent problem?
> I am doing query on a table using dozens(20-120) of scanners in
> parallel(multiple threads), trying to take advantage of the multiple cores.
> But I found the scan results doesn't consist among several goes. I have
> checked my code, seems there is no bug in it. So I guess the problem may
> come from the HBase itself.
> My HBase version is 0.20.3.
_________________________________________________________________
The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with
Hotmail.
http://www.windowslive.com/campaign/thenewbusy?tile=multicalendar&ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5
