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 28943101C6 for ; Tue, 9 Apr 2013 22:58:16 +0000 (UTC) Received: (qmail 30230 invoked by uid 500); 9 Apr 2013 22:58:15 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 30187 invoked by uid 500); 9 Apr 2013 22:58: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 30101 invoked by uid 99); 9 Apr 2013 22:58:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2013 22:58:15 +0000 Date: Tue, 9 Apr 2013 22:58:15 +0000 (UTC) From: "Ted Yu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8310) HBase snapshot timeout defautls and TableLockManger timeout 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-8310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627230#comment-13627230 ] Ted Yu commented on HBASE-8310: ------------------------------- @Jerry: Just curious: what does 'defautls' in the subject mean ? Thanks > HBase snapshot timeout defautls and TableLockManger timeout > ----------------------------------------------------------- > > Key: HBASE-8310 > URL: https://issues.apache.org/jira/browse/HBASE-8310 > Project: HBase > Issue Type: Bug > Components: snapshots > Affects Versions: 0.95.0 > Reporter: Jerry He > Assignee: Jerry He > Priority: Minor > Fix For: 0.98.0, 0.94.8, 0.95.2 > > > There are a few timeout values and defaults being used by HBase snapshot. > DEFAULT_MAX_WAIT_TIME (60000 milli sec, 1 min) for client response > TIMEOUT_MILLIS_DEFAULT (60000 milli sec, 1 min) for Procedure timeout > SNAPSHOT_TIMEOUT_MILLIS_DEFAULT (60000 milli sec, 1 min) for region server subprocedure > There is also other timeout involved, for example, > DEFAULT_TABLE_WRITE_LOCK_TIMEOUT_MS (10 mins) for TakeSnapshotHandler#prepare() > We could have this case: > The user issues a sync snapshot request, waits for 1 min, and gets an exception. > In the meantime the snapshot handler is blocked on the table lock, and the snapshot may continue to finish after 10 mins. > But the user will probably re-issue the snapshot request during the 10 mins. > This is a little confusing and messy when this happens. > To be more reasonable, we should either increase the DEFAULT_MAX_WAIT_TIME or decrease the table lock waiting time. -- 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