[
https://issues.apache.org/jira/browse/HBASE-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849418#action_12849418
]
Andrew Purtell commented on HBASE-2353:
---------------------------------------
Well worked example configs or some kind of wizard would be great to have, but
to get back on track a little that means sufficient flexibility in the
implementation to support those options. The proposal above to turn on and off
features on the write path according to flags is a good one, a generic and
extensible mechanism that can support many different policies. And, at no time
should we accept a change that permanently reduces performance without
providing a credible alternative, unless there is no such option.
> 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.
