hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-4487) The increment operation can release the rowlock before sync-ing the Hlog
Date Thu, 29 Sep 2011 06:57:46 GMT

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

dhruba borthakur updated HBASE-4487:
------------------------------------

    Attachment: appendNoSync5.txt

Addressed Ted Yu's review comments. The code that does 

{code}
      for (Entry e : pending) {
+        writer.append(e);
+      }
{code}

does not catch exceptions, instead throws an exception to the caller if any of the edits fail
to make it to HDFS. In fact, Hbase regionserver exits if an HDFS write/sync fails, this is
expected behaviour.
                
> The increment operation can release the rowlock before sync-ing the Hlog
> ------------------------------------------------------------------------
>
>                 Key: HBASE-4487
>                 URL: https://issues.apache.org/jira/browse/HBASE-4487
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>         Attachments: appendNoSync4.txt, appendNoSync5.txt
>
>
> This allows for better throughput when there are hot rows.I have seen this change make
a single row update improve from 400 increments/sec/server to 4000 increments/sec/server.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message