Hazelcast的IMAP升级到K8S上的5.1.1后停止工作
我们有一个“缓存”（javax.cache.cache）实现，它是Hazelcast的imap的包装器。我们使用复合对象密钥。
我们从版本3.12.5升级到5.1.1。当我在本地Windows机器上部署系统时，所有这些都可以很好地工作。但是，当我将系统部署到 kubernetes环境中时，地图“不起作用”。值不会持续到地图中（put操作之后）。 Hazelcast群集确实会形成，因此它似乎不是自动发现问题。我还有另一个K8S ENV，它确实可以正常工作。
我启用了Hazelcast的诊断模式，它似乎并没有向我展示任何有用的东西。我没有从com.hazelcast。*软件包中收到任何错误或警告。当我尝试4.x版时，同样的问题也发生了。
我正在尝试探索如何帮助意识到这里的问题。谢谢。
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.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
事实证明这是一个错误。 Hazelcast建议改用
0的值。Turns out it is a bug. Hazelcast recommends to use the value of
0instead.我遇到了同样的问题，但是我从Hazelcast 3.11.1到5.1.2迁移，我在“ com.hazelcast.map”中找到了IMAP，而不是在“ com.hazelcast.core”中。
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"