hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pranav Khaitan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2797) Another NPE in ReadWriteConsistencyControl
Date Wed, 07 Jul 2010 23:10:50 GMT

    [ https://issues.apache.org/jira/browse/HBASE-2797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12886149#action_12886149

Pranav Khaitan commented on HBASE-2797:

This patch doesn't fix the error I was getting. I see that the fix was only in the peek function.
However, the bug I am getting doesnt even touch the peek function. Just instantiating StoreScanner()
gives that error. It is possible that the instantiation is not done in the right context but
even then I would not expect this kind of error. I have attached a diff file which contains
the function I wrote for this bug (its just 4 lines)

> Another NPE in ReadWriteConsistencyControl
> ------------------------------------------
>                 Key: HBASE-2797
>                 URL: https://issues.apache.org/jira/browse/HBASE-2797
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.20.5
>            Reporter: Dave Latham
>            Assignee: ryan rawson
>            Priority: Blocker
>             Fix For: 0.20.6
>         Attachments: testDebugNPE.diff
> This occurred on a cluster with 46 slaves, running a couple MR jobs.  One doing heavy
writes copying everything from one table to a new table with a different schema.  After one
regionserver went down, about 40 of them died within an hour before it was caught and the
jobs stopped.  Let me know if any other piece of context would be particularly helpful.
> This exception appears in the .out file:
> Exception in thread "regionserver/" java.lang.NullPointerException
>         at org.apache.hadoop.hbase.regionserver.ReadWriteConsistencyControl.getThreadReadPoint(ReadWriteConsistencyControl.java:40)
>         at org.apache.hadoop.hbase.regionserver.MemStore$MemStoreScanner.getNext(MemStore.java:532)
>         at org.apache.hadoop.hbase.regionserver.MemStore$MemStoreScanner.seek(MemStore.java:558)
>         at org.apache.hadoop.hbase.regionserver.StoreScanner.reseek(StoreScanner.java:320)
>         at org.apache.hadoop.hbase.regionserver.StoreScanner.checkReseek(StoreScanner.java:306)
>         at org.apache.hadoop.hbase.regionserver.StoreScanner.peek(StoreScanner.java:143)
>         at org.apache.hadoop.hbase.regionserver.KeyValueHeap$KVScannerComparator.compare(KeyValueHeap.java:127)
>         at org.apache.hadoop.hbase.regionserver.KeyValueHeap$KVScannerComparator.compare(KeyValueHeap.java:117)
>         at java.util.PriorityQueue.siftDownUsingComparator(PriorityQueue.java:644)
>         at java.util.PriorityQueue.siftDown(PriorityQueue.java:612)
>         at java.util.PriorityQueue.poll(PriorityQueue.java:523)
>         at org.apache.hadoop.hbase.regionserver.KeyValueHeap.close(KeyValueHeap.java:151)
>         at org.apache.hadoop.hbase.regionserver.HRegion$RegionScanner.close(HRegion.java:1971)
>         at org.apache.hadoop.hbase.regionserver.HRegionServer.closeAllRegions(HRegionServer.java:1610)
>         at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:621)
>         at java.lang.Thread.run(Thread.java:619)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message