[
https://issues.apache.org/jira/browse/HBASE-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12848462#action_12848462
]
stack commented on HBASE-2353:
------------------------------
@Ryan What if for batch put, first we wrote all that is in the batch out to the
WAL and then per edit, you called the individual put method but with the
do-not-WAL flag set to true? Would that get you your speed back? But how to
treat errors? What do you tell the client if you've written the WAL but you
fail to update memstore? How were errors treated previously? Seems like you
have to reason about this stuff on a row by row basis?
> 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
>
>
> 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.
