Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C8EF711A44 for ; Tue, 22 Apr 2014 22:02:16 +0000 (UTC) Received: (qmail 14031 invoked by uid 500); 22 Apr 2014 22:02:15 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 13974 invoked by uid 500); 22 Apr 2014 22:02:15 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 13963 invoked by uid 99); 22 Apr 2014 22:02:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Apr 2014 22:02:15 +0000 Date: Tue, 22 Apr 2014 22:02:15 +0000 (UTC) From: "stack (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-11047) Remove TimeoutMontior MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-11047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977523#comment-13977523 ] stack commented on HBASE-11047: ------------------------------- That is a fun patch [~jxiang] Nice removals. +1 if it passes hadoopqa > Remove TimeoutMontior > --------------------- > > Key: HBASE-11047 > URL: https://issues.apache.org/jira/browse/HBASE-11047 > Project: HBase > Issue Type: Improvement > Components: Region Assignment > Reporter: Jimmy Xiang > Assignee: Jimmy Xiang > Priority: Minor > Attachments: hbase-11047.patch > > > With HBASE-8002, the TimeoutMonitor is disabled by default. Lately, we haven't see much problem of region assignments during integration testing with CM. I was thinking it may be time to remove the timeout monitor now? -- This message was sent by Atlassian JIRA (v6.2#6252)