hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ryan rawson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-3524) NPE from CompactionChecker
Date Sat, 12 Feb 2011 01:45:57 GMT

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

ryan rawson commented on HBASE-3524:
------------------------------------

the logic is:


             (this.ttl == HConstants.FOREVER || oldest < this.ttl)) {


so if we set oldest to MAX_VALUE then it will _never_ be smaller than this.ttl which is set
to 'length of time in ms an edit should live'.  Therefore it would be in the range from 1
-> MAX_VALUE, and by setting oldest to MIN_VALUE this branch will ALWAYS be true and prefer
to major compact a single file.

Make sense?

> NPE from CompactionChecker
> --------------------------
>
>                 Key: HBASE-3524
>                 URL: https://issues.apache.org/jira/browse/HBASE-3524
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.90.0
>            Reporter: James Kennedy
>            Assignee: ryan rawson
>            Priority: Blocker
>             Fix For: 0.90.1, 0.90.2
>
>         Attachments: 3524.txt
>
>
> I recently updated production data to use HBase 0.90.0.
> Now I'm periodically seeing:
> [10/02/11 17:23:27] 30076066 [mpactionChecker] ERROR nServer$MajorCompactionChecker 
- Caught exception
> java.lang.NullPointerException
> 	at org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:832)
> 	at org.apache.hadoop.hbase.regionserver.Store.isMajorCompaction(Store.java:810)
> 	at org.apache.hadoop.hbase.regionserver.HRegion.isMajorCompaction(HRegion.java:2800)
> 	at org.apache.hadoop.hbase.regionserver.HRegionServer$MajorCompactionChecker.chore(HRegionServer.java:1047)
> 	at org.apache.hadoop.hbase.Chore.run(Chore.java:66)
> The only negative effect is that this is interrupting compactions from happening. But
that is pretty serious and this might be a sign of data corruption?
> Maybe it's just my data, but this task should at least involve improving the handling
to catch the NPE and still iterate through the other onlineRegions that might compact without
error.  The MajorCompactionChecker.chore() method only catches IOExceptions and so this NPE
breaks out of that loop. 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message