You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2012/12/18 03:42:13 UTC
[jira] [Commented] (HBASE-7375) Acquire readLock do not apply
timeout in flushcache
[ https://issues.apache.org/jira/browse/HBASE-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534560#comment-13534560 ]
Ted Yu commented on HBASE-7375:
-------------------------------
Seems to be duplicate of HBASE-7376
> Acquire readLock do not apply timeout in flushcache
> ---------------------------------------------------
>
> Key: HBASE-7375
> URL: https://issues.apache.org/jira/browse/HBASE-7375
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.96.0, 0.94.4
> Reporter: binlijin
> Fix For: 0.96.0, 0.94.4
>
>
> {code}
> HRegion
> public boolean flushcache() throws IOException {
> lock(lock.readLock());
> }
> {code}
> The HRegion.flushcache is called by the normal flush cache, so if we use a timeout, the MemStoreFlusher may be get a RegionTooBusyException, it is safe to do not use a timeout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira