![]() The default value for cluster connection timeout for clients has been set as -1 (infinite timeout): Used for storing user data, per-entry statistics of maps now are disabled by default they were enabled in ![]() Seeing that getting entry level statistics in a map has not beenĪ common use case and it has been creating unnecessary memory overhead that can be otherwise See the Dynamically Changing Log Levels section. Such as rack, fault domain, power sources, network, and resources of a virtual machine in a zone.ĭynamic Log Level Support: Added the support of changing Hazelcast log levels You can group members according to their placement metadata provided by the cloud providers, Partition grouping mechanism in the Hazelcast discovery plugin for AWS. Placement Aware Partition Grouping: Added the support of Of the IMDG Reference Manual for more information. Provided by this plugin and on which the containers/pods run. You can create partition groups according to the name of the node which is Partition grouping mechanism in the Hazelcast discovery plugin for Kubernetes. Node Aware Partition Grouping: Added the support of Limit the count of results, or skip some results. You can see the query results being ordered in ascending or descending fashion, ![]() Sorting Support for Hazelcast SQL: Added the support of SQL sorting feature.īy using the newly implemented ORDER BY, LIMIT, and OFFSET constructions, Premature removal of the lately added but not yet accessed map entries. The LRU eviction policy now takes last access time value into account to prevent 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |