hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1784) Missing rows after medium intensity insert
Date Wed, 26 Aug 2009 19:47:59 GMT

    [ https://issues.apache.org/jira/browse/HBASE-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748108#action_12748108
] 

stack commented on HBASE-1784:
------------------------------

@Mathias If you grep /hdfs/hadoop/hbase/domirama/377086364/batchid/5233728315379016023 in
your namenode log or 7352946847213562224 (from blk_7352946847213562224_926536) do you see
anything interesting?  The file looks like its been deleted by another process (doubly assigned
region?  But this is RC2, right?).

> 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
>         Attachments: DataLoad.java, HBASE-1784.log
>
>
> 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.


Mime
View raw message