You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2013/01/05 01:45:04 UTC
[jira] [Commented] (HBASE-7376) Acquiring readLock does not apply
timeout in HRegion#flushcache
[ https://issues.apache.org/jira/browse/HBASE-7376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13544473#comment-13544473 ]
Hudson commented on HBASE-7376:
-------------------------------
Integrated in HBase-0.94-security-on-Hadoop-23 #10 (See [https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/10/])
HBASE-7376 Acquiring readLock does not apply timeout in HRegion#flushcache (binlijin) (Revision 1423553)
Result = FAILURE
jxiang :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
> Acquiring readLock does not apply timeout in HRegion#flushcache
> ---------------------------------------------------------------
>
> Key: HBASE-7376
> URL: https://issues.apache.org/jira/browse/HBASE-7376
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Affects Versions: 0.96.0, 0.94.4
> Reporter: binlijin
> Assignee: binlijin
> Fix For: 0.96.0, 0.94.4
>
> Attachments: HBASE-7376-94.patch, HBASE-7376-trunk.patch
>
>
> {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