hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18233) We shouldn't wait for readlock in doMiniBatchMutation in case of deadlock
Date Tue, 22 Aug 2017 04:20:00 GMT

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

stack commented on HBASE-18233:

What [~carp84] says. I tried to cherry-pick this forward but fails at first hurdle, 1.3.

And for the record, the affirmation from user has evaporated. They now think it was a change
in their client app that was more responsible for speedup.

I think this the way to go. User said it made things better if perhaps not as good as old
mechanism. Lets get it in. Hopefully next complaint is more reproducible or works closer to
upstream.  Thanks.

> We shouldn't wait for readlock in doMiniBatchMutation in case of deadlock
> -------------------------------------------------------------------------
>                 Key: HBASE-18233
>                 URL: https://issues.apache.org/jira/browse/HBASE-18233
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 1.2.7
>            Reporter: Allan Yang
>            Assignee: Allan Yang
>            Priority: Blocker
>             Fix For: 2.0.0, 1.4.0, 1.3.2, 1.2.7
>         Attachments: HBASE-18233-branch-1.2.patch, HBASE-18233-branch-1.2.v2.patch, HBASE-18233-branch-1.2.v3.patch,
> Please refer to the discuss in HBASE-18144
> https://issues.apache.org/jira/browse/HBASE-18144?focusedCommentId=16051701&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16051701

This message was sent by Atlassian JIRA

View raw message