hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Spiegelberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-5886) Add new metric for possible data loss due to puts without WAL
Date Mon, 30 Apr 2012 17:55:49 GMT

    [ https://issues.apache.org/jira/browse/HBASE-5886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13265055#comment-13265055

Nicolas Spiegelberg commented on HBASE-5886:

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


View raw message