hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13379) TimeRangeTracker Can Be Non-Blocking
Date Wed, 01 Apr 2015 16:13:53 GMT

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

stack commented on HBASE-13379:

[~jleach] What Matteo said. I tried a few variants. Need to show evidence last attempt is
good. If you have better suggestion, appreciated. Can I close this if you think it a dup of

> TimeRangeTracker Can Be Non-Blocking
> ------------------------------------
>                 Key: HBASE-13379
>                 URL: https://issues.apache.org/jira/browse/HBASE-13379
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: John Leach
>            Assignee: John Leach
>            Priority: Minor
>   Original Estimate: 2h
>  Remaining Estimate: 2h
> I am seeing the TimeRangeTracker hotspot under heavy write load.  It looks like a good
use case for an atomic reference for the data point (min and max timestamp).  I have a working
proto, will submit patch for consideration once I run this test suite (beast).

This message was sent by Atlassian JIRA

View raw message