I am currently working on a context where the application uses Hazelcast. The paradigm used is not embedded, therefore server-client is used. I am having a flow where on a distributed map is executed a query. After all the optimizations I could think of, different combinations with memory format, query cache, indexes etc. The most I could achieve was around
Tag: hazelcast
using the Hazelcast distributed locks with Coroutines in Kotlin and Spring webflux
My question is as the documentation says, fencedlocks are reentrant locks for “THREADS” and I am using spring boot with Kotlin and webflux so in my application I am using Coroutines for concurrency and as you probably know spring webflux provides an event-loop with a limited number of threads to fulfilling the Coroutines, what will happen if I use this
What is the recommended max message size in Hazelcast?
I’m trying to understand the recommended max message size in Hazelcast. The best documentation I can find is https://docs.hazelcast.com/hazelcast/5.0/capacity-planning where it says An optimum partition size is between 50MB – 100MB Does this mean messages should be smaller in size than that limit? Is there a way I can pass around messages that are 1Gb in size? Is this recommended?
How to synchronize method with HazelCast between two nodes?
There is Spring Boot project. Project works on two nodes. I have method for send message mail with scheduler. The message is sent 2 times, since two nodes are working. How can I use HazelCast to configure the method so that it works once, only by one, more optimal node? There is very little documentation and articles on the net.
Configure Hazelcast via external yml-file
I´ve a running hzc-yml configuration in classpath – the generated jar file works fine in a docker context. Now I want to load this yml-file externally. I added this startup-property to my DOCKERFILE: The whole DOCKERFILE looks like: It seems that the service wants to apply the external yml-file, but I always get this error: hzc-service | /bin/sh: ./hazelcast.yaml: Permission