Class CachingMap<K,V>
- All Implemented Interfaces:
Map<K,
V>
- Direct Known Subclasses:
NearCache
If the back map implements ObservableMap interface, the CachingMap provides four different strategies of invalidating the front map entries that have changed by other processes in the back map:
- LISTEN_NONE strategy instructs the cache not to listen for invalidation events at all. This is the best choice for raw performance and scalability when business requirements permit the use of data which might not be absolutely current. Freshness of data can be guaranteed by use of a sufficiently brief eviction policy for the front map;
- LISTEN_PRESENT strategy instructs the CachingMap to listen to the back map events related only to the items currently present in the front map. This strategy works best when each instance of a front map contains distinct subset of data relative to the other front map instances (e.g. sticky data access patterns);
- LISTEN_ALL strategy instructs the CachingMap to listen to all back map events. This strategy is optimal for read-heavy tiered access patterns where there is significant overlap between the different instances of front maps;
- LISTEN_AUTO strategy instructs the CachingMap implementation to switch automatically between LISTEN_PRESENT and LISTEN_ALL strategies based on the cache statistics;
- LISTEN_LOGICAL strategy instructs the CachingMap to listen to all back map events that are not synthetic deletes. A synthetic event could be emitted as a result of eviction or expiration. With this invalidation strategy, it is possible for the front map to contain cache entries that have been synthetically removed from the back (though any subsequent re-insertion will cause the corresponding entries in the front map to be invalidated).
The front map implementation is assumed to be thread safe; additionally
any modifications to the front map are allowed only after the corresponding
lock is acquired against the ControlMap
.
Note: null values are not cached in the front map and therefore this implementation is not optimized for maps that allow null values to be stored.
- Author:
- ag/gg 2002.09.10, gg 2003.10.16
-
Nested Class Summary
Modifier and TypeClassDescriptionprotected class
DeactivationListener for the back NamedCache.protected class
MapListener for front map responsible for deregistering back map listeners upon front map eviction.protected class
MapListener for back map responsible for keeping the front map coherent with the back map.protected class
MapListener for back map responsible for keeping the front map coherent with the back map. -
Field Summary
Modifier and TypeFieldDescriptionstatic final int
Invalidation strategy that instructs the CachingMap to listen to all back map events; this strategy is preferred when updates to the back map are frequent and with high probability come from the outside of this CachingMap; for example multiple CachingMap instances using the same back map with a large degree of key set overlap between front maps.static final int
Invalidation strategy that instructs the CachingMap implementation to switch automatically between LISTEN_PRESENT and LISTEN_ALL strategies based on the cache statistics.static final int
Invalidation strategy that instructs the CachingMap to listen to all back map events that are not synthetic deletes.static final int
No invalidation strategy.static final int
Invalidation strategy that instructs the CachingMap to listen to the back map events related only to the items currently present in the front map; this strategy serves best when the changes to the back map come mostly from the CachingMap itself.protected com.tangosol.internal.net.NamedCacheDeactivationListener
The NamedCache deactivation listener.protected int
The current invalidation strategy, which at times could be different from the target strategy.protected int
The invalidation strategy that this map is to use. -
Constructor Summary
ConstructorDescriptionConstruct a CachingMap using two specified maps: FrontMap (aka "cache", "near" or "shallow") and BackMap (aka "actual", "real" or "deep").Construct a CachingMap using two specified maps: FrontMap (aka "cache", "near" or "shallow") and BackMap (aka "actual", "real" or "deep") and using the specified front map invalidation strategy. -
Method Summary
Modifier and TypeMethodDescriptionvoid
clear()
Clears both the front and back maps.boolean
containsKey
(Object oKey) boolean
containsValue
(Object oValue) protected int
Ensure that a strategy has been chosen and that any appropriate global listeners have been registered.entrySet()
getAll
(Collection<? extends K> colKeys) Get all the specified keys, if they are in the cache.getAllFromFrontMap
(Collection<? extends K> colKeys) Retrieve entries from the front map.Obtain the back map reference.Obtain the CacheStatistics for this cache.Obtain the ConcurrentMap that should be used to synchronize the front map modification access.Obtain the front map reference.long
Determine the rough number of front map invalidation hits since the cache statistics were last reset.long
Determine the rough number of front map invalidation misses since the cache statistics were last reset.int
Obtain the invalidation strategy used by this CachingMap.long
Determine the total number ofregisterListener(Object oKey)
operations since the cache statistics were last reset.protected MapListener
instantiateBackMapListener
(int nStrategy) Factory pattern: instantiate back map listener.protected CachingMap<K,
V>.FrontMapListener Factory pattern: instantiate front map listener.protected void
invalidateFront
(Object oKey) Invalidate the key from the front.protected boolean
isCheckPrimingExclusively
(boolean fPriming) Return true if we can rely on the server emitting priming events (based on receiving a at least one priming event from a storage node).protected boolean
Determine if changes to the back map affect the front map so that data in the front map stays in sync.boolean
isEmpty()
protected boolean
Check if the specified event is a "priming" one.keySet()
Implementation of put method that optionally skips the return value retrieval and allows to specify an expiry for the cache entry.void
protected void
Instantiate and register a DeactivationListener with the back cache.protected void
Register the global front map listener.protected void
Register the global back map listener.protected void
registerListener
(Object oKey) Register the back map listener for the specified key.protected void
registerListeners
(Set setKeys) Register the back map listeners for the specified set of keys.void
release()
Release the CachingMap.protected void
Remove the key holder from the ThreadLocal object.void
Reset the front map.protected void
Reset the "current invalidation strategy" flag.protected Set
Set up a thread local Set to hold all the keys that might be evicted from the front cache.int
size()
Return the number of key-value mappings in this map.toString()
For debugging purposes, format the contents of the CachingMap in a human readable format.Lock the keys in the given set without blocking.protected void
Unregister back cache deactivation listener.protected void
Unregister the global front map listener.protected void
Unregister the global back map listener.protected void
unregisterListener
(Object oKey) Unregister the back map listener for the specified key.protected void
unregisterListeners
(Set<K> setKeys) Unregister the back map listener for the specified keys.protected void
Unregister an associated CacheMBean.protected void
Validate the front map entry for the specified back map event.values()
Obtain an collection of the values contained in this map.Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
Methods inherited from interface java.util.Map
compute, computeIfAbsent, computeIfPresent, equals, forEach, getOrDefault, hashCode, merge, putIfAbsent, remove, replace, replace, replaceAll
-
Field Details
-
LISTEN_NONE
public static final int LISTEN_NONENo invalidation strategy.- See Also:
-
LISTEN_PRESENT
public static final int LISTEN_PRESENTInvalidation strategy that instructs the CachingMap to listen to the back map events related only to the items currently present in the front map; this strategy serves best when the changes to the back map come mostly from the CachingMap itself.- See Also:
-
LISTEN_ALL
public static final int LISTEN_ALLInvalidation strategy that instructs the CachingMap to listen to all back map events; this strategy is preferred when updates to the back map are frequent and with high probability come from the outside of this CachingMap; for example multiple CachingMap instances using the same back map with a large degree of key set overlap between front maps.- See Also:
-
LISTEN_AUTO
public static final int LISTEN_AUTOInvalidation strategy that instructs the CachingMap implementation to switch automatically between LISTEN_PRESENT and LISTEN_ALL strategies based on the cache statistics.- See Also:
-
LISTEN_LOGICAL
public static final int LISTEN_LOGICALInvalidation strategy that instructs the CachingMap to listen to all back map events that are not synthetic deletes. A synthetic event could be emitted as a result of eviction or expiration. With this invalidation strategy, it is possible for the front map to contain cache entries that have been synthetically removed from the back (though any subsequent re-insertion will cause the corresponding entries in the front map to be invalidated).- See Also:
-
m_nStrategyTarget
protected int m_nStrategyTargetThe invalidation strategy that this map is to use. -
m_nStrategyCurrent
protected int m_nStrategyCurrentThe current invalidation strategy, which at times could be different from the target strategy. -
m_listenerDeactivation
protected com.tangosol.internal.net.NamedCacheDeactivationListener m_listenerDeactivationThe NamedCache deactivation listener.
-
-
Constructor Details
-
CachingMap
Construct a CachingMap using two specified maps:- FrontMap (aka "cache", "near" or "shallow") and
- BackMap (aka "actual", "real" or "deep").
LISTEN_AUTO
strategy.- Parameters:
mapFront
- front mapmapBack
- back map- See Also:
-
CachingMap
Construct a CachingMap using two specified maps:- FrontMap (aka "cache", "near" or "shallow") and
- BackMap (aka "actual", "real" or "deep")
- Parameters:
mapFront
- front mapmapBack
- back mapnStrategy
- specifies the strategy used for the front map invalidation; valid values are LISTEN_* constants
-
-
Method Details
-
release
public void release()Release the CachingMap. If the BackMap implements an ObservableMap calling this method is necessary to remove the BackMap listener. Any access to the CachingMap which has been released will cause IllegalStateException. -
getFrontMap
Obtain the front map reference.Note: direct modifications of the returned map may cause an unpredictable behavior of the CachingMap.
- Returns:
- the front Map
-
getBackMap
Obtain the back map reference.Note: direct modifications of the returned map may cause an unpredictable behavior of the CachingMap.
- Returns:
- the back Map
-
getInvalidationStrategy
public int getInvalidationStrategy()Obtain the invalidation strategy used by this CachingMap.- Returns:
- one of LISTEN_* values
-
getControlMap
Obtain the ConcurrentMap that should be used to synchronize the front map modification access.- Returns:
- a ConcurrentMap controlling the front map modifications
-
isCoherent
protected boolean isCoherent()Determine if changes to the back map affect the front map so that data in the front map stays in sync.- Returns:
- true if the front map has a means to stay in sync with the back map so that it does not contain stale data
-
getCacheStatistics
Obtain the CacheStatistics for this cache.- Returns:
- a CacheStatistics object
-
clear
public void clear()Clears both the front and back maps. -
containsKey
- Specified by:
containsKey
in interfaceMap<K,
V>
-
containsValue
- Specified by:
containsValue
in interfaceMap<K,
V>
-
entrySet
-
get
-
getAll
Get all the specified keys, if they are in the cache. For each key that is in the cache, that key and its corresponding value will be placed in the map that is returned by this method. The absence of a key in the returned map indicates that it was not in the cache, which may imply (for caches that can load behind the scenes) that the requested data could not be loaded.Note: this implementation does not differentiate between missing keys or null values stored in the back map; in both cases the returned map will not contain the corresponding entry.
- Parameters:
colKeys
- a collection of keys that may be in the named cache- Returns:
- a Map of keys to values for the specified keys passed in col
- Since:
- Coherence 2.5
-
getAllFromFrontMap
Retrieve entries from the front map.- Parameters:
colKeys
- a collection of keys- Returns:
- a Map of keys to values for a subset of the passed in keys that exist in the front map
-
tryLock
Lock the keys in the given set without blocking.- Parameters:
setKeys
- keys to lock in the control map- Returns:
- Set of keys that were successfully locked
-
isPriming
Check if the specified event is a "priming" one.- Parameters:
evt
- the event- Returns:
true
if the specified event is a "priming" one
-
isCheckPrimingExclusively
protected boolean isCheckPrimingExclusively(boolean fPriming) Return true if we can rely on the server emitting priming events (based on receiving a at least one priming event from a storage node).- Parameters:
fPriming
- whether the event that instigated this check is a priming event- Returns:
- true if we can rely on the server emitting priming events
-
isEmpty
public boolean isEmpty() -
keySet
-
put
-
put
Implementation of put method that optionally skips the return value retrieval and allows to specify an expiry for the cache entry.- Parameters:
oKey
- the keyoValue
- the valuefReturn
- if true, the return value is required; otherwise the return value will be ignoredcMillis
- the number of milliseconds until the cache entry will expire- Returns:
- previous value (if required)
- Throws:
UnsupportedOperationException
- if the requested expiry is a positive value and either the front map or the back map implementations do not support the expiration functionality- See Also:
-
putAll
-
invalidateFront
Invalidate the key from the front. The caller must have the key locked.- Parameters:
oKey
- the key to invalidate
-
validate
Validate the front map entry for the specified back map event.- Parameters:
evt
- the MapEvent from the back map
-
remove
-
size
public int size()Return the number of key-value mappings in this map. Expensive: always reflects the contents of the underlying cache. -
values
Obtain an collection of the values contained in this map. If there is a listener for the back map, then the collection will be mutable; otherwise the returned collection will be immutable. The returned collection reflects the full contents of the back map. -
getInvalidationHits
public long getInvalidationHits()Determine the rough number of front map invalidation hits since the cache statistics were last reset.An invalidation hit is an externally induced map event for an entry that exists in the front map.
- Returns:
- the number of cache invalidation hits
-
getInvalidationMisses
public long getInvalidationMisses()Determine the rough number of front map invalidation misses since the cache statistics were last reset. An invalidation miss is an externally induced map event for an entry that does not exists in the front map.- Returns:
- the number of cache invalidation misses
-
getTotalRegisterListener
public long getTotalRegisterListener()Determine the total number ofregisterListener(Object oKey)
operations since the cache statistics were last reset.- Returns:
- the total number of listener registrations
-
toString
For debugging purposes, format the contents of the CachingMap in a human readable format. -
registerListener
protected void registerListener()Register the global back map listener. -
unregisterListener
protected void unregisterListener()Unregister the global back map listener. -
registerListener
Register the back map listener for the specified key.- Parameters:
oKey
- the key
-
registerListeners
Register the back map listeners for the specified set of keys.- Parameters:
setKeys
- the key set
-
unregisterListener
Unregister the back map listener for the specified key.- Parameters:
oKey
- the key
-
unregisterListeners
Unregister the back map listener for the specified keys.Note: all the keys in the passed-in set must be locked and will be unlocked.
- Parameters:
setKeys
- Set of keys to unregister (and unlock)
-
setKeyHolder
Set up a thread local Set to hold all the keys that might be evicted from the front cache.- Returns:
- a Set to hold all the keys in the ThreadLocal object or null if the bulk unregistering is not needed
-
removeKeyHolder
protected void removeKeyHolder()Remove the key holder from the ThreadLocal object. -
registerFrontListener
protected void registerFrontListener()Register the global front map listener. -
unregisterFrontListener
protected void unregisterFrontListener()Unregister the global front map listener. -
ensureInvalidationStrategy
protected int ensureInvalidationStrategy()Ensure that a strategy has been chosen and that any appropriate global listeners have been registered.- Returns:
- the current strategy
-
resetInvalidationStrategy
protected void resetInvalidationStrategy()Reset the "current invalidation strategy" flag.This method should be called only while the access to the front map is fully synchronised and the front map is empty to prevent stalled data.
-
instantiateBackMapListener
Factory pattern: instantiate back map listener.- Parameters:
nStrategy
- the strategy to instantiate a back map listener for- Returns:
- an instance of back map listener responsible for keeping the front map coherent with the back map
-
registerDeactivationListener
protected void registerDeactivationListener()Instantiate and register a DeactivationListener with the back cache. -
unregisterDeactivationListener
protected void unregisterDeactivationListener()Unregister back cache deactivation listener. -
resetFrontMap
public void resetFrontMap()Reset the front map. -
unregisterMBean
protected void unregisterMBean()Unregister an associated CacheMBean. -
instantiateFrontMapListener
Factory pattern: instantiate front map listener.- Returns:
- an instance of front map listener
-