[
https://issues.apache.org/jira/browse/HBASE-12457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14206010#comment-14206010
]
Lars Hofhansl commented on HBASE-12457:
---------------------------------------
Sometime (but not always) we Splits interspersed with this.
While l scoured over the code I noticed the following:
* SplitTransaction write CREATE_SPLIT_DIR after it created the daugther dirs
and CLOSED_PARENT_REGION after the parent region is closed
* Upon rollback writestate.writesEnabled is set back to true unconditionally at
the CREATE_SPLIT_DIR stage.
It seems that should only be done when we journaled CLOSED_PARENT_REGION.
> Regions in transition for a long time when CLOSE interleaves with a slow
> compaction
> -----------------------------------------------------------------------------------
>
> Key: HBASE-12457
> URL: https://issues.apache.org/jira/browse/HBASE-12457
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.7
> Reporter: Lars Hofhansl
>
> Under heave load we have observed regions remaining in transition for 20
> minutes when the master requests a close while a slow compaction is running.
> The pattern is always something like this:
> # RS starts a compaction
> # HM request the region to be closed on this RS
> # Compaction is not aborted for another 20 minutes
> # The region is in transition and not usable.
> In every case I tracked down so far the time between the requested CLOSE and
> abort of the compaction is almost exactly 20 minutes, which is suspicious.
> Of course part of the issue is having compactions that take over 20 minutes,
> but maybe we can do better here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
