Open prtk-fyndna opened 11 months ago
This seems to be due to Dapr using a really old version of the Hazelcast SDK.
A workaround is to use Hazelcast 3.12.12 -
docker run -e JAVA_OPTS="-Dhazelcast.local.publicAddress=127.0.0.1:5701" -p 5701:5701 hazelcast/hazelcast:3.12.12
The underlying SDK needs to be upgraded to use 4.x/5.x Hazelcast versions. Note, this might break the existing users using 3.x clients, so we can consider an alpha v2 release with the latest SDK version.
@shubham1172 Hazelcast is an Alpha component, and it is also hardly used (and we use a very old pre-release version of the SDK). As such I am ok with a breaking change in this component. At this point however, this will miss the 1.12 release and can go into 1.13. I do not support creating a separate version - this would bring in another dependency with memory and goroutine implications. So the existing component should just be updated.
If two versions are required I request that this is done via pluggable components. We will not include two component versions in the runtime itself.
As @shubham1172 said, at this time please use Hazelcast 3.X. In Dapr 1.13 we will look into upgrading this.
We have cut the 1.12 release branch - so at this time we can start accepting a PR for the Hazelcast library upgrade against our components-contrib master branch.
Expected Behavior
Dapr application starts with Hazelcast as a state store.
Actual Behavior
State store component loading failed, resulting in application termination
Steps to Reproduce the Problem
Dapr CLI version: 1.3.0 Dapr Runtime version: 1.11.2 Hazelcast version: 5.3.1
Logs
Dapr
Hazelcast