Hazelcast's IMap stopped working after upgrading to version 5.1.1 on K8S

Question

We have an "cache" (javax.cache.Cache) implementation that is a wrapper of Hazelcast's IMap. We use a composite Object key.

We upgraded from version 3.12.5 to 5.1.1. When I deploy the system on a local Windows machine, all works well. But when I deploy the system into an Kubernetes environment, the map just "does not work". Values do not get persisted into the map (after a put operation). An Hazelcast cluster does get formed so it does not seem to be an auto discovery issue. I also have another K8S env in which it does work properly.

I enabled Hazelcast's diagnostic mode and it does not seem to show me anything useful. I do not get any error or warn messages from the com.hazelcast.* package. The same issue happened also when I tried version 4.x.

I am trying to explore ways which will help to the realise what is the issue here. Thank you.

Answer 1

Turns out it is a bug. Hazelcast recommends to use the value of 0 instead.

Answer 2

I had the same problem but i was migrating from hazelcast 3.11.1 to 5.1.2, I found the IMap in "com.hazelcast.map" not in "com.hazelcast.core"