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

Hadoop QA commented on HBASE-13530:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12727215/HBASE-13530-v1.patch
  against master branch at commit 2bf8cda4f68940909e9bcfdf8ae41cc751a49c7d.
  ATTACHMENT ID: 12727215

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/13776//console

This message is automatically generated.

> 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: 0.98.13
>
>         Attachments: 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)

Reply via email to