[
https://issues.apache.org/jira/browse/HBASE-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749972#action_12749972
]
stack commented on HBASE-1784:
------------------------------
In this latest run, Mathias is seeing:
{code}
13:06 <hbs_> hbase-hadoop-master-hadooptux-00.gicm.net.log:2009-09-01
14:34:30,214 DEBUG org.apache.hadoop.hbase.master.BaseScanner: GET got values
when meta found none: serverAddress=10.154.99.180:60020, startCode=1251791310025
13:06 <hbs_> hbase-hadoop-master-hadooptux-00.gicm.net.log:2009-09-01
14:34:31,473 DEBUG org.apache.hadoop.hbase.master.BaseScanner: GET got values
when meta found none: serverAddress=10.154.99.180:60020, startCode=1251791310025
13:06 <hbs_> hbase-hadoop-master-hadooptux-00.gicm.net.log:2009-09-01
14:36:29,485 DEBUG org.apache.hadoop.hbase.master.BaseScanner: GET got values
when meta found none: serverAddress=10.154.99.180:60020, startCode=1251791310025
13:06 <hbs_> hbase-hadoop-master-hadooptux-00.gicm.net.log:2009-09-01
14:36:29,494 DEBUG org.apache.hadoop.hbase.master.BaseScanner: GET got values
when meta found none: serverAddress=10.154.99.180:60020, startCode=1251791310025
{code}
These are cases where the content of the row has changed between the scan of
the row and inside in the method where we check for assignment. Each instance
above would have made for a double-assignment, if my understanding is correct.
> Missing rows after medium intensity insert
> ------------------------------------------
>
> Key: HBASE-1784
> URL: https://issues.apache.org/jira/browse/HBASE-1784
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.20.0
> Reporter: Jean-Daniel Cryans
> Priority: Blocker
> Fix For: 0.20.0
>
> Attachments: 1784-v2.patch, 1784.patch, DataLoad.java,
> dbl-assignment-20090831, double-assignment,
> HBASE-1784-StoreFileScanner-hack.patch, HBASE-1784.log, META.log,
> processSplitRegion-check-regionIsOpening.patch
>
>
> This bug was uncovered by Mathias in his mail "Issue on data load with
> 0.20.0-rc2". Basically, somehow, after a medium intensity insert a lot of
> rows goes missing. Easy way to reproduce : PE. Doing a PE scan or randomRead
> afterwards won't uncover anything since it doesn't bother about null rows.
> Simply do a count in the shell, easy to test (I changed my scanner caching in
> the shell to do it faster).
> I tested some light insertions with force flush/compact/split in the shell
> and it doesn't break.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
