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 0CC2E1761A for ; Sat, 25 Apr 2015 09:03:40 +0000 (UTC) Received: (qmail 90781 invoked by uid 500); 25 Apr 2015 09:03:39 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 90660 invoked by uid 500); 25 Apr 2015 09:03:39 -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 90397 invoked by uid 99); 25 Apr 2015 09:03:39 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 25 Apr 2015 09:03:39 +0000 Date: Sat, 25 Apr 2015 09:03:39 +0000 (UTC) From: "Victor Xu (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-13530) Add param for bulkload wait duration in HRegion. 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-13530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14512356#comment-14512356 ] Victor Xu commented on HBASE-13530: ----------------------------------- Yes, I agree. > Add param for bulkload wait duration in HRegion. > ------------------------------------------------ > > Key: HBASE-13530 > URL: https://issues.apache.org/jira/browse/HBASE-13530 > Project: HBase > Issue Type: Improvement > Components: regionserver > Affects Versions: 0.98.12 > Reporter: Victor Xu > Priority: Minor > Fix For: 2.0.0, 0.98.13 > > Attachments: HBASE-13530-0.98-v2.patch, HBASE-13530-0.98.patch, HBASE-13530-master-v2.patch, HBASE-13530-master.patch, HBASE-13530-v1.patch > > > In our scenario, incremental read/write operations and complete bulkload operations are mixed together. Bulkload needs write lock while read/write and flush/compact need read lock. When a region is compacting, the bulkload could hang at writeLock.tryLock(waitDuration, TimeUnit) method. The original default waitDuration is 60sec (from 'hbase.busy.wait.duration'), and this could block all read/writes operations from acquiring read lock for 1 minute. The chances of this scenario become high when compaction speed limit feature(HBASE-8329) is used. > Maybe we need to decrease the wait duration ONLY for bulkload, and let read/write keep theirs. So I add this param('hbase.bulkload.wait.duration') to tune wait duration for bulkloading. Of course, it is a table level setting, and the default value is from original logic. -- This message was sent by Atlassian JIRA (v6.3.4#6332)