hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chia-Ping Tsai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18753) Introduce the unsynchronized TimeRangeTracker
Date Thu, 07 Sep 2017 17:23:00 GMT

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

Chia-Ping Tsai commented on HBASE-18753:

bq, Segment needs Sync version of TR where as Immutable Segments can have Simple version
Will address it as a follow up

bq. Why name this way? NON_SYNC? That is not correct name?
Will replace it by ASYNC (thanks! Ted)

bq. This can make a non sync version of TR right?
ya, no one use it in multi-threading env. Will change it from SYNC to ASYNC.

Thanks. [~anoop.hbase]

> Introduce the unsynchronized TimeRangeTracker
> ---------------------------------------------
>                 Key: HBASE-18753
>                 URL: https://issues.apache.org/jira/browse/HBASE-18753
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>             Fix For: 2.0.0-alpha-3
>         Attachments: HBASE-18753.v0.patch
> If HBASE-18752 is pushed, it will be better to introduce the unsync TimeRangeTracker
for reducing the cost of recalculation.

This message was sent by Atlassian JIRA

View raw message