[
https://issues.apache.org/jira/browse/HBASE-27648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17690808#comment-17690808
]
Hudson commented on HBASE-27648:
--------------------------------
Results for branch master
[build #778 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/778/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/778/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/778/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/778/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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: 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)
