New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MultiMapValue can not be serialized #13559
Comments
@rvega-arg thanks for the great report! let's see what we can do about it. |
Fixes hazelcast#13559 Multimap does not have MERGE listener anyway hence it's pointless to fire MERGE events. I also added additional parameters to the MultiMap split-brain test to test every merge policy for both BINARY and OBJECT formats.
@rvega-arg: once again thanks for your bug report! It turns out the event should not be published at all hence no need to have the value serializable. Before we release the fix you can disable multimap merging after split-brain: Configure |
@jerrinot i couldn't found the gitlab issue but at some point i remember that hazelcast is now supporting MultiMap merge after split brain. This change is breaking that feature? Maybe i miss understood something. Thanks! |
@rvega-arg: yes, you are right. Hazelcast 3.10 introduced merging policies for many structures. A merge policy is a function to merge entries from 2 clusters when a partitioned cluster is healed. If you configure the |
Fixes hazelcast#13559 Multimap does not have MERGE listener anyway hence it's pointless to fire MERGE events. I also added additional parameters to the MultiMap split-brain test to test every merge policy for both BINARY and OBJECT formats.
Fixes hazelcast#13559 Multimap does not have MERGE listener anyway hence it's pointless to fire MERGE events. I also added additional parameters to the MultiMap split-brain test to test every merge policy for both BINARY and OBJECT formats.
I'm using vertx with the latest version of hazelcast 3.10.4. Vertx use hazelcast as default implementation for its cluster manager service. However i am getting a few errors when running vertx+hazelcast in a distributed cluster.
After a couple of hours of research i found that vertx cluster goes into an inconsistent state because it use a MultiMap to hold some internal information. However when split brain happens and this multimap should be merged, hazelcast fail with
I think MultiMapValue should implement IdentifiedDataSerializable. I made a quick implementation and it works, but i 'm not sure if my code is good enough
The text was updated successfully, but these errors were encountered: