[
https://issues.apache.org/jira/browse/HBASE-1984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell resolved HBASE-1984.
-----------------------------------
Resolution: Duplicate
Several recent issues duplicate this issue, but do it better.
> Clearly document durability versus write performance tradeoff
> -------------------------------------------------------------
>
> Key: HBASE-1984
> URL: https://issues.apache.org/jira/browse/HBASE-1984
> Project: Hadoop HBase
> Issue Type: Task
> Reporter: Andrew Purtell
> Fix For: 0.21.0
>
>
> Hadoop 0.21 now has a reliable append and flush feature and this gives us the
> opportunity to review some assumptions. The current situation:
> * Every edit going to a catalog table is flushed so there's no data loss.
> * The user tables edits are flushed every hbase.regionserver.flushlogentries
> which by default is 100.
> We should call out the durability versus write performance tradeoff in the
> flushlogentries description and up on the wiki somewhere, maybe on
> http://wiki.apache.org/hadoop/PerformanceTuning . We should also provide two
> example configurations, one for performance (err on the performance side but
> not insane) and one for paranoia.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
