hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phabricator (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-6930) [89-fb] Avoid acquiring the same row lock repeatedly
Date Wed, 03 Oct 2012 22:19:08 GMT

     [ https://issues.apache.org/jira/browse/HBASE-6930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Phabricator updated HBASE-6930:

    Attachment: D5841.2.patch

mbautin updated the revision "[jira] [HBASE-6930] [89-fb] Fix TestThriftServerLegacy: notifyAll
should be inside synchronized block, and a null checkAndMutate expected value should be handled
Reviewers: Kannan, Liyin, Karthik, JIRA

  Adding ThriftServerRunner fixes



To: Kannan, Liyin, Karthik, JIRA, mbautin

> [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

View raw message