tessob

@alparslanavci no, we have no proxy/service mesh. Our Service manifest is similar to [this one](https://github.com/hazelcast/hazelcast-kubernetes#creating-service). There are just two pods in separate namespace now. However cluster itself is bigger. Our...

Short update, I have checked out morning logs with 20K attempts to find other nodes and then taken a look at source codes to comprehend where the client has got...

Hi @leszko, 1. We have tested as in guide, in the same k8s cluster and namespace, and everything is OK. Logs: ``` ######################################## # JAVA_OPTS=-Djava.net.preferIPv4Stack=true -Dhazelcast.logging.type=log4j2 -Dlog4j.configurationFile=/opt/hazelcast/log4j2.properties -XX:MaxRAMPercentage=80.0 -XX:MaxGCPauseMillis=5 --add-modules...

Short update, I have tested my application in the minikube locally and everything is OK. So the root-cause of such behavior highly likely in K8s cluster and/or deployment manifests. However,...

After I disabled it I still have the same behavior in logs, so there should be another cause.

> Hi @tessob , were you able to find out the cause? I'm currently experiencing the same issue. I'm also in AWS EKS Sorry for A late reply )) I...

@AshishWat No, just forget about Hazelcast after code observation and moved to Infinispan. So far so good.