Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 29 Oct 2012 16:46:14 +0000 (UTC)
From: "Jimmy Xiang (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <1858057232.39549.1351529174300.JavaMail.jiratomcat@arcas>
In-Reply-To: 
 <1803940959.2527.1325633800793.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Comment Edited] (HBASE-5119) Set the TimeoutMonitor's
 timeout back down
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-5119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481975#comment-13481975 ] 

Jimmy Xiang edited comment on HBASE-5119 at 10/29/12 4:45 PM:
--------------------------------------------------------------

Based on my testing for HBASE-6611/HBASE-6977, in my testing cluster, I can easily open 10+k regions on 4 nodes in around 4 minutes.  I think we are fine to set the timeout back to 5 minutes.
                
      was (Author: jxiang):
    Based on my testing for HBASE-6611/HBASE-6977, in my testing cluster, I can easily open 10+ regions on 4 nodes in around 4 minutes.  I think we are fine to set the timeout back to 5 minutes.
                  
> Set the TimeoutMonitor's timeout back down
> ------------------------------------------
>
>                 Key: HBASE-5119
>                 URL: https://issues.apache.org/jira/browse/HBASE-5119
>             Project: HBase
>          Issue Type: Task
>    Affects Versions: 0.92.0
>            Reporter: Jean-Daniel Cryans
>            Priority: Blocker
>             Fix For: 0.96.0
>
>         Attachments: trunk_5119.patch
>
>
> The TimeoutMonitor used to be extremely racy and caused more troubles than it fixed, but most of this has been fixed I believe in the context of 0.92 so I think we should set it down back to a useful level. Currently it's 30 minutes, what should the new value be?
> I think 5 minutes should be good, will do some testing.

--
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