You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Santosh Banerjee (JIRA)" <ji...@apache.org> on 2014/08/20 21:52:28 UTC

[jira] [Commented] (HBASE-2353) HBASE-2283 removed bulk sync optimization for multi-row puts

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

Santosh Banerjee commented on HBASE-2353:
-----------------------------------------

Hi,

I wanted to see the file diff for the fix to this issue, but it seems http://review.hbase.org/r/167 is broken.
Could someone point me to the diff url?

If it's migrated to git, how do I get the pull request,if any.

-thanks
SB

> HBASE-2283 removed bulk sync optimization for multi-row puts
> ------------------------------------------------------------
>
>                 Key: HBASE-2353
>                 URL: https://issues.apache.org/jira/browse/HBASE-2353
>             Project: HBase
>          Issue Type: Bug
>            Reporter: ryan rawson
>            Assignee: Todd Lipcon
>            Priority: Blocker
>              Labels: moved_from_0_20_5
>             Fix For: 0.90.0
>
>         Attachments: HBASE-2353_def_log_flush.patch, hbase-2353.txt
>
>
> previously to HBASE-2283 we used to call flush/sync once per put(Put[]) call (ie: batch of commits).  Now we do for every row.  
> This makes bulk uploads slower if you are using WAL.  Is there an acceptable solution to achieve both safety and performance by bulk-sync'ing puts?  Or would this not work in face of atomic guarantees?
> discuss!



--
This message was sent by Atlassian JIRA
(v6.2#6252)