[
https://issues.apache.org/jira/browse/HBASE-2353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849411#action_12849411
]
Jonathan Gray commented on HBASE-2353:
--------------------------------------
There are probably some jiras laying around for some kind of CLI that would
generate configuration after taking some user input about their requirements,
cluster information, etc... Could boil that into there if it ever gets done.
But since those things are always nice-to-haves that rarely get built, shipping
with a few sample hbase-site's could be a good solution.
Part of the initial setup in the docs would be to decide which to use and
rename it to hbase-site.xml.
Even still, there will need to be defaults, so can we still fight about 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.
