hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-18233) We shouldn't wait for readlock in doMiniBatchMutation in case of deadlock
Date Thu, 30 Nov 2017 23:28:00 GMT

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

stack edited comment on HBASE-18233 at 11/30/17 11:27 PM:
----------------------------------------------------------

Bad forward-port. 1.3+ adjusts timeout waiting on locks with different exceptions for timeout
vs failed get of lock. Weaving the original patch in I made a mistake. I was testing whether
it a deadline timeout vs whether we should wait on locks at all.... 


was (Author: stack):
Bad forward-port. 1.3+ adjusts timeout waiting on locks with different exceptions for timeout
vs failed get of lock. Weaving the original patch in I made a mistake.

> 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: 1.3.2, 1.4.1, 1.2.7
>
>         Attachments: HBASE-18233-branch-1.2.patch, HBASE-18233-branch-1.2.trivial.patch,
HBASE-18233-branch-1.2.v2.patch, HBASE-18233-branch-1.2.v3.patch, HBASE-18233-branch-1.2.v4
(1).patch, HBASE-18233-branch-1.2.v4 (1).patch, HBASE-18233-branch-1.2.v4 (2).patch, HBASE-18233-branch-1.2.v4.patch,
HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch,
HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v4.patch,
HBASE-18233-branch-1.2.v4.patch, HBASE-18233-branch-1.2.v5 (1).patch, HBASE-18233-branch-1.2.v5.patch,
HBASE-18233-branch-1.2.v5.patch, HBASE-18233-branch-1.2.v6.patch, HBASE-18233.branch-1.2.UT.log,
HBASE-18233.branch-1.3.001.patch, HBASE-18233.branch-1.3.001.patch, HBASE-18233.branch-1.3.002.patch,
HBASE-18233.branch-1.3.002.patch, HBASE-18233.branch-1.3.003.patch, HBASE-18233.branch-1.3.003.patch,
HBASE-18233.branch-1.4.001.patch, HBASE-18233.branch-1.4.002.patch, HBASE-18233.branch-1.4.002.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
(v6.4.14#64029)

Mime
View raw message