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

Hadoop QA commented on HBASE-14643:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12767509/HBASE-14643_v2.patch
  against master branch at commit c1f0442045f44fcbb3935f9244794929a5d0caea.
  ATTACHMENT ID: 12767509

    {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:green}+1 hadoop versions{color}. The patch compiles with all 
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.6.1 2.7.0 
2.7.1)

    {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:red}-1 checkstyle{color}.  The applied patch generated 
1748 checkstyle errors (more than the master's current 1747 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 post-site goal succeeds with this patch.

     {color:red}-1 core tests{color}.  The patch failed these unit tests:
                       org.apache.hadoop.hbase.regionserver.TestStoreFile

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

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

This message is automatically generated.

> Avoid Splits from once again opening a closed reader for fetching the first 
> and last key
> ----------------------------------------------------------------------------------------
>
>                 Key: HBASE-14643
>                 URL: https://issues.apache.org/jira/browse/HBASE-14643
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>    Affects Versions: 2.0.0
>            Reporter: ramkrishna.s.vasudevan
>            Assignee: Heng Chen
>         Attachments: HBASE-14643.patch, HBASE-14643_v1.patch, 
> HBASE-14643_v2.patch
>
>
> Currently split flow is such that we close the parent region and all its 
> store file readers are also closed.  After that inorder to split the 
> reference files we need the first and last keys for which once again open the 
> readers on those store files.  This could be costlier operation considering 
> the fact that it has to contact the HDFS for this close and open operation. 
> This JIRA is to see if we can improve this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to