hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-7375) Acquire readLock do not apply timeout in flushcache
Date Wed, 19 Dec 2012 06:05:21 GMT

     [ https://issues.apache.org/jira/browse/HBASE-7375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lars Hofhansl resolved HBASE-7375.
----------------------------------

       Resolution: Duplicate
    Fix Version/s:     (was: 0.94.4)
                       (was: 0.96.0)

Yes. It's a dup. closing.
                
> 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
>
> {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

Mime
View raw message