<p>After a fresh deployment of our application on a kubernetes cluster we always will end up with a hazelcast network partitioning problem (split brain).</p>

<p>All three replicas starting at the same time. Hazelcast is configured to use the jhipster-registry (i.e. Eureka) for discovery. At the time, the application tries to initialize hazelcast, no instance is registered in the registry which gives us three independet hazelcast nodes.</p>

<p>The documentation says that hazelcast will detect this and merge all my maps. But this does not happen.</p>

<p>BTW</p>

Guido Zockoll
<p>Can you try using Hazelcast Kubernetes discovery plugin:  <a href="https://github.com/hazelcast/hazelcast-kubernetes" rel="nofollow noreferrer">https://github.com/hazelcast/hazelcast-kubernetes</a></p>

<p>This should work out of the box.</p>
