hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13530) Add param for bulkload wait duration in HRegion.
Date Fri, 24 Apr 2015 04:39:38 GMT

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

Hadoop QA commented on HBASE-13530:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against master branch at commit 031dd3638cff1310d85ce8ba62d2278f5ef1a904.
  ATTACHMENT ID: 12727805

    {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
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions
(2.4.1 2.5.2 2.6.0)

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 protoc{color}.  The applied patch does not increase the total number of
protoc compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

    {color:green}+1 checkstyle{color}.  The applied patch does not increase the total number
of checkstyle errors

    {color:green}+1 findbugs{color}.  The patch does not introduce any  new Findbugs (version
2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

     {color:red}-1 core tests{color}.  The patch failed these unit tests:

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/13792//testReport/
Release Findbugs (version 2.0.3) 	warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/13792//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/13792//artifact/patchprocess/checkstyle-aggregate.html

  Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/13792//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-0.98.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

View raw message