You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "John Leach (JIRA)" <ji...@apache.org> on 2015/04/01 17:53:53 UTC

[jira] [Assigned] (HBASE-13379) TimeRangeTracker Can Be Non-Blocking

     [ https://issues.apache.org/jira/browse/HBASE-13379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Leach reassigned HBASE-13379:
----------------------------------

    Assignee: John Leach

> 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
(v6.3.4#6332)