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

Hadoop QA commented on HBASE-13896:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12739410/HBASE-13896-0.98-v1.patch
  against 0.98 branch at commit 293506c7cdef3e866c75a7b92558a423eb804d11.
  ATTACHMENT ID: 12739410

    {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.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:red}-1 javadoc{color}.  The javadoc tool appears to have generated 
25 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:green}+1 core tests{color}.  The patch passed unit tests in .

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

  Javadoc warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/14398//artifact/patchprocess/patchJavadocWarnings.txt
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/14398//console

This message is automatically generated.

> Multi-actions in hbase-client could fall in dead loop when region moves.
> ------------------------------------------------------------------------
>
>                 Key: HBASE-13896
>                 URL: https://issues.apache.org/jira/browse/HBASE-13896
>             Project: HBase
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 0.98.13
>            Reporter: Victor Xu
>            Assignee: Victor Xu
>            Priority: Minor
>         Attachments: HBASE-13896-0.98-v1.patch
>
>
> The code in AsyncProcess.receiveGlobalFailure() use only one row to update 
> region cache in hbase-client. When we use HTable.put(List<Put>) api to write 
> some data which are from different regions and some of them are 
> moved/balanced while writing, the client may fall into a dead loop: 
> multi-actions fails because some regions moved => update only one region 
> cache(not the wrong ones) => resubmit => failed again.
> It only happens in 0.98 branch, and the master branch is ok.
> The patch followed should update all cached region locations when 
> multi-actions fails.



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

Reply via email to