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

Posted to issues@hbase.apache.org by "Bryan Beaudreault (Jira)" <ji...@apache.org> on 2024/04/23 17:56:00 UTC

[jira] [Updated] (HBASE-27648) CopyOnWriteArrayMap does not honor contract of ConcurrentMap.putIfAbsent

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

Bryan Beaudreault updated HBASE-27648:
--------------------------------------
    Fix Version/s: 2.6.0

> CopyOnWriteArrayMap does not honor contract of ConcurrentMap.putIfAbsent
> ------------------------------------------------------------------------
>
>                 Key: HBASE-27648
>                 URL: https://issues.apache.org/jira/browse/HBASE-27648
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Bryan Beaudreault
>            Assignee: Bryan Beaudreault
>            Priority: Major
>              Labels: patch-available
>             Fix For: 2.6.0, 3.0.0-alpha-4, 2.4.17, 2.5.4
>
>
> I've been tracking down a meta cache issue and noticed this. I'm not sure if this is actually causing an issue, but if you enable TRACE logs on MetaCache it causes all calls to cacheLocation to go down the "Merged cached locations" path instead of the "Cached location" path for inserting new entries. This is just misleading, but also means going through the more expensive RegionLocations.mergeLocations. Reading the code, I don't think that would cause an actual issue, but hard to be sure.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)