Skip to content
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

Do not fire MERGE events when merging MultiMap entries #13703

Merged

Conversation

jerrinot
Copy link
Contributor

@jerrinot jerrinot commented Sep 6, 2018

Fixes #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.

Backport will follow.

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.
@@ -133,6 +142,11 @@ protected void onAfterSplitBrainCreated(HazelcastInstance[] firstBrain, Hazelcas
multiMapA2 = secondBrain[0].getMultiMap(multiMapNameA);
multiMapB2 = secondBrain[0].getMultiMap(multiMapNameB);

EntryListener<Object, Object> listener = new EmptyEntryListener<Object, Object>();
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is the important bit for the test

@jerrinot jerrinot merged commit 6132455 into hazelcast:master Sep 10, 2018
@jerrinot jerrinot deleted the fixes/multimap-listener-split-brain/master branch September 10, 2018 12:24
@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Apr 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MultiMapValue can not be serialized
3 participants