[
https://issues.apache.org/jira/browse/HBASE-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849367#action_12849367
]
Andrew Purtell commented on HBASE-2353:
---------------------------------------
I disagree. I think higher performing options should be the default. I want
durability as much if not more that others. However, the only users of out of
the box configurations are prototypers, evaluators, and benchmarkers (and in
this last case only the naïve ones) and it is good strategy to seek to avoid
being labeled slow again by new users, unnecessarily. Any move into production
requires some attention paid to configuration changes and tuning. As long as we
provide clear guidance and detail what deferred log flushing trades away, we
get the best result here in my opinion.
> 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.
