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

["Manukranth Kolloju (JIRA)" <ji...@apache.org>]

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

Manukranth Kolloju commented on HBASE-6930:
-------------------------------------------

I was reviewing the changes from 0.89-fb that didn't go to open source trunk. This seems to be one of them. At first glance on the diff, this doesn't seem to be present in master. Earlier reviewers, any thoughts on this one ?

> [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: HBASE-6930.diff
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)