[
https://issues.apache.org/jira/browse/HBASE-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13265055#comment-13265055
]
Nicolas Spiegelberg edited comment on HBASE-5886 at 4/30/12 5:55 PM:
---------------------------------------------------------------------
I'm confused about why this metric is useful. This metric is never accurate at
determining data loss because querying it is async from the Put path. If you
are looking for a restart point, you should have another thread call
HTable.flush() and checkpoint or add an API to query for the latest timestamp
in a CF's storefile.
Edit: s/and/at
was (Author: nspiegelberg):
I'm confused about why this metric is useful. This metric is never
accurate and determining data loss because querying it is async from the Put
path. If you are looking for a restart point, you should have another thread
call HTable.flush() and checkpoint or add an API to query for the latest
timestamp in a CF's storefile.
> Add new metric for possible data loss due to puts without WAL
> --------------------------------------------------------------
>
> Key: HBASE-5886
> URL: https://issues.apache.org/jira/browse/HBASE-5886
> Project: HBase
> Issue Type: New Feature
> Components: metrics, regionserver
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Labels: metrics
> Attachments: HBASE-5886-v0.patch, HBASE-5886-v1.patch,
> HBASE-5886-v2.patch
>
>
> Add a metrics to keep track of puts without WAL and possible data loss size.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
