hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mathias Herberts (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1780) HTable.flushCommits clears write buffer in finally clause
Date Thu, 27 Aug 2009 09:52:59 GMT

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

Mathias Herberts commented on HBASE-1780:

I think we should specify somewhere that HTable instances are not safe to use in MT environments
for writes.

The manipulation of writebuffer could could lead to ConcurrentModificationException being
raised if Puts are added to it while the new write buffer size is computed in flushCommits.

> HTable.flushCommits clears write buffer in finally clause
> ---------------------------------------------------------
>                 Key: HBASE-1780
>                 URL: https://issues.apache.org/jira/browse/HBASE-1780
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: client
>         Environment: All
>            Reporter: Mathias Herberts
>             Fix For: 0.20.1, 0.21.0
>         Attachments: HBASE-1780.patch
> Metthod flushCommits clears the write buffer in a finally clause.
> When using the write buffer, if the call to processBatchOfRows done in flushCommits throws
an exception, the write buffer will be cleared thus potentially leading to loss of data on
the client side.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message