[jira] [Commented] (HBASE-13896) Multi-actions in hbase-client could fall in dead loop when region moves.

["Victor Xu (JIRA)" <ji...@apache.org>]

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

Victor Xu commented on HBASE-13896:
-----------------------------------

After I used this patch for nearly 4 weeks, my cluster got a very weird problem that the client' Get requests got stuck occasionally during regions balancing. It may be some side-effect from my previous patch, and I will continue to track this issue and do more tests.

> 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
>             Fix For: 0.98.14
>
>         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)