Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Not A Problem
-
None
-
None
-
None
Description
Usages of putIfAbsent in Geode on ConcurrentHashMap may not have realized the actual synchronized/atomic nature of the putIfAbsent. See https://bugs.openjdk.java.net/browse/JDK-6737839
This ticket is for someone to review or possibly change the putIfAbsent usages to be more performant.
Not sure if putIfAbsent is called enough and under contention enough for this to matter...
Attachments
Attachments
Issue Links
- is related to
-
GEODE-6404 review use of computeIfAbsent across code base
- Closed