hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Heng Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14279) Race condition in ConcurrentIndex
Date Tue, 10 Nov 2015 06:30:11 GMT

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

Heng Chen commented on HBASE-14279:

Where else we need this Heng Chen? KeyLocker?
yeah,  currently IdLock,  KeyLocker  NOT use MultiMap inside.
IMO if concurrent conflicts is not heavy,  may be we can use MultiMap to reduce memory used.

Of course, it has no relates with this issue.  we can come back when we really need to do

Thanks for your suggestion [~ikeda] and [~stack]. 
I will move ConcurrentIndex into BucketCache.  

> Race condition in ConcurrentIndex
> ---------------------------------
>                 Key: HBASE-14279
>                 URL: https://issues.apache.org/jira/browse/HBASE-14279
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Hiroshi Ikeda
>            Assignee: Heng Chen
>            Priority: Minor
>         Attachments: HBASE-14279.patch, HBASE-14279_v2.patch, HBASE-14279_v3.patch, HBASE-14279_v4.patch,
> {{ConcurrentIndex.put}} and {{remove}} are in race condition. It is possible to remove
a non-empty set, and to add a value to a removed set. Also {{ConcurrentIndex.values}} is vague
in sense that the returned set sometimes trace the current state and sometimes doesn't.

This message was sent by Atlassian JIRA

View raw message