You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/05/08 22:44:04 UTC

[jira] [Commented] (HBASE-17210) Set timeout on trying rowlock according to client's RPC timeout

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

stack commented on HBASE-17210:
-------------------------------

[~yangzhe1991] What brought about this change? Were you experiencing contention on a row? Asking because seeing something where all handlers are blocked trying to get a lock but weirdly no handler seems to have the lock; i.e. no one is doing work.


> Set timeout on trying rowlock according to client's RPC timeout
> ---------------------------------------------------------------
>
>                 Key: HBASE-17210
>                 URL: https://issues.apache.org/jira/browse/HBASE-17210
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Phil Yang
>            Assignee: Phil Yang
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: HBASE-17120.v1.patch, HBASE-17210.branch-1.v01.patch, HBASE-17210.branch-1.v02.patch, HBASE-17210.branch-1.v03.patch, HBASE-17210.v02.patch, HBASE-17210.v03.patch, HBASE-17210.v04.patch, HBASE-17210.v04.patch
>
>
> Now when we want to get a row lock, the timeout is fixed and default is 30s. But the requests from client have different RPC timeout setting. We can use the client's deadline to set timeout on tryLock.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)