You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Dave Latham (JIRA)" <ji...@apache.org> on 2013/06/27 14:50:22 UTC

[jira] [Commented] (HBASE-6930) [89-fb] Avoid acquiring the same row lock repeatedly

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

Dave Latham commented on HBASE-6930:
------------------------------------

Definitely confused here, along with Lars.  Did the change describe (avoid acquiring the same row lock) happen somewhere else?  Discussing something similar in HBASE-8806.
                
> [89-fb] Avoid acquiring the same row lock repeatedly
> ----------------------------------------------------
>
>                 Key: HBASE-6930
>                 URL: https://issues.apache.org/jira/browse/HBASE-6930
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Liyin Tang
>         Attachments: D5841.1.patch, D5841.2.patch
>
>
> When processing the multiPut, multiMutations or multiDelete operations, each IPC handler thread tries to acquire a lock for each row key in these batches. If there are duplicated row keys in these batches, previously the IPC handler thread will repeatedly acquire the same row key again and again.
> So the optimization is to sort each batch operation based on the row key in the client side, and skip acquiring the same row lock repeatedly in the server side.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira