You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/10/27 19:57:07 UTC

[jira] Commented: (HBASE-963) Fix the retries in HTable.flushCommit

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

stack commented on HBASE-963:
-----------------------------

Patch is fine  -- would suggest that before commit, change the close so it just notes exception rather than close it since on close, there is nothing much that can be done about and IOE.

> Fix the retries in HTable.flushCommit
> -------------------------------------
>
>                 Key: HBASE-963
>                 URL: https://issues.apache.org/jira/browse/HBASE-963
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: client
>            Reporter: Jean-Daniel Cryans
>            Assignee: Jean-Daniel Cryans
>            Priority: Blocker
>             Fix For: 0.19.0
>
>         Attachments: hbase-963-ugly.patch
>
>
> Many are seeing writes not getting into tables since HBASE-748 was committed. As I explained to Jonathan: 
> <jdcryans> jgray: but I'm pretty sure that under high load a split took too long and the write didn't get through
> <jdcryans> jgray: That part has to be refactored to be used with other kind of batching
> <jdcryans> jgray: because the exponential backoff retry logic is in HCM but I had to get the retry out of it...
> So this issue is about getting the retry logic out of HTable, hopefully merging it with the rest of HCM.

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