hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Latham (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3974) Client: Ability to Discard Bad HTable Puts
Date Thu, 09 Jun 2011 23:02:59 GMT

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

Dave Latham commented on HBASE-3974:


I've seen the same thing happen with auto flush off, when calling flushCommits.

> Client: Ability to Discard Bad HTable Puts
> ------------------------------------------
>                 Key: HBASE-3974
>                 URL: https://issues.apache.org/jira/browse/HBASE-3974
>             Project: HBase
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.89.20100924, 0.90.3, 0.92.0
>            Reporter: Nicolas Spiegelberg
>            Assignee: Nicolas Spiegelberg
>            Priority: Critical
>             Fix For: 0.90.4
> While debugging an application consistency issue, we noticed that a single, synchronous
Put request threw a NoServerForRegionException but eventually succeeded 90 seconds later.
 The problem is that failed put requests are not actually removed from the HTable's writeBuffer.
 This makes sense for asynchronous puts using setAutoFlush(false) but don't make sense for
the default case where we expect synchronous operation.  We should discard all failed puts
for the synchronous case and provide an API so asynchronous requests can have their failed
puts cleared.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message