[
https://issues.apache.org/jira/browse/HBASE-13262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365911#comment-14365911
]
Jonathan Lawlor commented on HBASE-13262:
-----------------------------------------
I believe that 1.0.0 is also affected by the underlying issue (still not sure
what that actual cause is). When I ran your test on branch-1.0 with the Scan
configuration from branch-1+ (i.e. caching=Integer.Max_Value and
maxResultSize=2MB) I saw this at the output:
{quote}
2015-03-17 12:51:59,123 INFO [main] hbase.HBaseTest(167): Wrote 1000000 entries
2015-03-17 12:51:59,123 INFO [main] hbase.HBaseTest(182): Wrote 1000000
entries in total
2015-03-17 12:51:59,123 INFO [main] hbase.HBaseTest(185): Closing table used
for writes
2015-03-17 12:51:59,127 DEBUG [main] client.ClientScanner(260): Advancing
internal scanner to startKey at '1\x00'
2015-03-17 12:51:59,327 DEBUG [main] client.ClientScanner(260): Advancing
internal scanner to startKey at '2\x00'
2015-03-17 12:51:59,412 DEBUG [main] client.ClientScanner(260): Advancing
internal scanner to startKey at '3\x00'
2015-03-17 12:51:59,477 DEBUG [main] client.ClientScanner(260): Advancing
internal scanner to startKey at '4\x00'
2015-03-17 12:51:59,528 DEBUG [main] client.ClientScanner(260): Advancing
internal scanner to startKey at '5\x00'
2015-03-17 12:51:59,567 INFO [main] hbase.HBaseTest(204): Saw row 500253
2015-03-17 12:51:59,597 DEBUG [main] client.ClientScanner(260): Advancing
internal scanner to startKey at '6\x00'
2015-03-17 12:51:59,641 DEBUG [main] client.ClientScanner(260): Advancing
internal scanner to startKey at '7\x00'
2015-03-17 12:51:59,683 DEBUG [main] client.ClientScanner(260): Advancing
internal scanner to startKey at '8\x00'
2015-03-17 12:51:59,713 DEBUG [main] client.ClientScanner(260): Advancing
internal scanner to startKey at '9\x00'
2015-03-17 12:51:59,729 INFO [main] hbase.HBaseTest(204): Saw row 801761
2015-03-17 12:51:59,742 INFO [main] hbase.HBaseTest(211): Last row in Result
902495
2015-03-17 12:51:59,742 INFO [main] hbase.HBaseTest(214): Saw 23590 rows
2015-03-17 12:51:59,743 INFO [main] hbase.HBaseTest(215): Saw 235900 cells
2015-03-17 12:51:59,881 INFO [main] hbase.HBaseTest(220): Missing 976410
rows:...
....
{quote}
As [~elserj] called out above, it seems that we are jumping between regions too
early. This hypothesis is also supported by the fact that if you remove the
splits from table creation then the issue does not occur. Sorry, my intention
is not to hijack this issue, just trying to provide some information that may
lead us to the cause.
> ResultScanner doesn't return all rows in Scan
> ---------------------------------------------
>
> Key: HBASE-13262
> URL: https://issues.apache.org/jira/browse/HBASE-13262
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 2.0.0, 1.1.0
> Environment: Single node, pseduo-distributed 1.1.0-SNAPSHOT
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Blocker
> Fix For: 2.0.0, 1.1.0
>
>
> Tried to write a simple Java client again 1.1.0-SNAPSHOT.
> * Write 1M rows, each row with 1 family, and 10 qualifiers (values [0-9]),
> for a total of 10M cells written
> * Read back the data from the table, ensure I saw 10M cells
> Running it against {{04ac1891}} (and earlier) yesterday, I would get ~20% of
> the actual rows. Running against 1.0.0, returns all 10M records as expected.
> [Code I was
> running|https://github.com/joshelser/hbase-hwhat/blob/master/src/main/java/hbase/HBaseTest.java]
> for the curious.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
