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

Liang Xie commented on HBASE-9894:
----------------------------------

[~saint....@gmail.com], yes
[~lhofhansl], totally agreed with you, i also doesn't understand why he enabled 
it:)  anyway, let's remove it, it should be encounterd even in a debug/dev env 
with "-ea" possible right? we shouldn't abort the whole server instance in this 
case.

> remove the inappropriate assert statement in Store.getSplitPoint()
> ------------------------------------------------------------------
>
>                 Key: HBASE-9894
>                 URL: https://issues.apache.org/jira/browse/HBASE-9894
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>    Affects Versions: 0.94.6, 0.94.12
>            Reporter: Liang Xie
>            Assignee: Liang Xie
>            Priority: Minor
>         Attachments: HBase-9894-0.94.txt
>
>
> One of my friend encountered a RS abort issue frequently during loading data. 
> Here is the log stack:
> FATAL org.apache.hadoop.hbase.regionserver.HRegionServer: ABORTING region 
> server gdc-dn49-formal.i.nease.net,60020,138320
> 3883151: Uncaught exception in service thread regionserver60020.cacheFlusher
> java.lang.AssertionError: getSplitPoint() called on a region that can't split!
>         at 
> org.apache.hadoop.hbase.regionserver.Store.getSplitPoint(Store.java:1926)
>         at 
> org.apache.hadoop.hbase.regionserver.RegionSplitPolicy.getSplitPoint(RegionSplitPolicy.java:79)
>         at 
> org.apache.hadoop.hbase.regionserver.HRegion.checkSplit(HRegion.java:5603)
>         at 
> org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:415)
>         at 
> org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:387)
>         at 
> org.apache.hadoop.hbase.regionserver.MemStoreFlusher.run(MemStoreFlusher.java:250)
>         at java.lang.Thread.run(Thread.java:662)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to