[
https://issues.apache.org/jira/browse/HBASE-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved HBASE-2363.
--------------------------------
Resolution: Duplicate
this has been somewhat addressed by hbase.skip.errors and
hbase.hlog.split.skip.errors, implemented elsewhere
> Add configuration for tunable dataloss sensitivity
> --------------------------------------------------
>
> Key: HBASE-2363
> URL: https://issues.apache.org/jira/browse/HBASE-2363
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.20.3, 0.90.0
> Reporter: Todd Lipcon
>
> There are many cases in HBase when the process detects that some data is "not
> quite right". We often have two choices: (a) throw up our hands and exit, or
> (b) log a warning and push through the issue, potentially losing data. I
> think some users are very sensitive to dataloss and would prefer that the
> system become unavailable rather than continue with potentially lost data.
> Other users just want the system to stay up, and if they lose a log segment
> it's fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
