[
https://issues.apache.org/jira/browse/HBASE-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849017#action_12849017
]
Todd Lipcon commented on HBASE-2353:
------------------------------------
bq. Another thing to watch out for is people running the default config then
writing nasty email/twitter notes because our out of the box performance isnt
good unless you do tweaks X,Y,Z
I think this is simply a matter of education. I personally care less about the
opinions of people on twitter than I do about correct operation. Correct
operation has its costs. HBase has been "cheating" for some time and hence had
great performance. I am certain that it's going to be slower once it's correct,
and absolutely OK with that.
> 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.
