[
https://issues.apache.org/jira/browse/HBASE-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849333#action_12849333
]
Kannan Muthukkaruppan commented on HBASE-2353:
----------------------------------------------
Having "durable" semantics as the default, and providing an optional "sloppy"
overload of Put (which does the deferredLogFlush optimization) seems better to
me.
With regards to making the basic multi-row Put case faster, I guess it would
help the single-threaded client case the most. If the client was already
multi-threaded, then the group commit benefits would already be kicking in to
amortize the cost of the syncs. Todd's suggestion of optimistically acquiring
locks in batches of rows sounds good to me.
> HBASE-2283 removed bulk sync optimization for multi-row puts
> ------------------------------------------------------------
>
> Key: HBASE-2353
> URL: https://issues.apache.org/jira/browse/HBASE-2353
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: ryan rawson
> Fix For: 0.21.0
>
> Attachments: HBASE-2353-deferred.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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
