'Hazelcast - Objects stored in near cache (client side) are evicted very quickly when we migrate to Hazelcast 4

We use Hazelcast for many years with version 3.9 on an application which used the near cache mechanism (we store data in the OBJECT format). This application is connected to an Hazelcast cluster of 3 nodes. Configuration of the near cache

    void nearCacheConfig(ClientConfig clientConfig) {
        NearCacheConfig nearCacheConfig = new NearCacheConfig();
        nearCacheConfig.setName("*" + AbstractCache.NEAR_CACHE_DISCRIMINATORY);
        // Useful to avoid serializing object in near cache
        nearCacheConfig.setInMemoryFormat(InMemoryFormat.OBJECT);
        clientConfig.addNearCacheConfig(nearCacheConfig);
    }

Recently, we tried to update to version 4.1 and we experiment huge performance problems. After some researches, we found that data of the near cache are very quickly evicted (without any update of the cache) - about 5-10 seconds maximum.

Does anyone know if the standard mechanism of the near cache eviction have changed between versions 3.9 and 4.1? We tried many configurations and we also tried the last Hazelcast version (4.2.2) but we still have the same issue.

javahazelcastnear-cache


Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source

Related Questions