Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 18 Dec 2012 05:40:15 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12624394.1355796203267.21319.1355809215762@arcas>
In-Reply-To: <JIRA.12624394.1355796203267@arcas>
References: <JIRA.12624394.1355796203267@arcas>
Subject: [jira] [Updated] (HBASE-7376) Acquiring readLock does not apply
 timeout in HRegion#flushcache
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ted Yu updated HBASE-7376:
--------------------------

    Summary: Acquiring readLock does not apply timeout in HRegion#flushcache  (was: Acquire readLock do not apply timeout in flushcache)
    
> 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