When the policy is PER_NODE and the cluster is scaled downįixed an issue where the map’s Near Cache was setting its maximum size as 10.000Įven if the configured eviction policy is NONE. Now, the Hazelcast member fails to start, i.e., fast fails, in such a case.įixed an issue where the maximum size policy for a map was being ignored

Previously, this configuration inconsistency was causing the related member Require the per-entry statistics to be enabled. Some merge policies like LatestUpdateMergePolicy for the map and WAN replication configurations #19483įixed an issue where the health monitor was incorrectly showing theįixed an issue where the updates made to a persistent map store might be lost This has been fixed by making these commands' implementations strictly follow the memcached protocol specification.įixed an issue where the totalPublishes statistics for the Reliable Topic data structure were always generated as 0.įixed an issue where the map.clear() and cache.clear() methods were evicting all entries in all near caches of all the maps in a cluster, not only the map on which these methods are called.įixed an issue that caused some map entries to remain in Hazelcast even when you configured eviction or expiration. Hazelcast’s memcached implementation was interpreting the number values and parameters for incr and decr wrongly (numbers were being converted into byte arrays instead of decimals). Fixed an issue where the statistics like puts and removals were not increasing when these operations are executed through Transactional interface.įixed an issue where Hazelcast clients, which have only the IP address of a member to connect (but the member also has a hostname), were not able to connect to the cluster.

4.2.8 mapping major