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

Fix/3.0/issue 724 #728

Merged
merged 1 commit into from Aug 20, 2013
Merged

Conversation

gurbuzali
Copy link
Contributor

No description provided.

mdogan added a commit that referenced this pull request Aug 20, 2013
@mdogan mdogan merged commit 081a9a8 into hazelcast:maintenance-3.x Aug 20, 2013
@mmedenjak mmedenjak added the Source: Internal PR or issue was opened by an employee label Apr 13, 2020
devOpsHazelcast pushed a commit that referenced this pull request Feb 15, 2024
…728)

As identified in HZ-4343, it is currently not possible to WAN replicate
from 1 cluster to multiple other clusters when all clusters share the
same cluster name. This is because the
`AbstractWanPublisher#publishReplicationEventInternal` method checks and
maintains each batch event's list of cluster names, returning early if
the list already contains the target cluster's name.

This check is done to prevent infinite loops when forwarding
(republishing) is enabled - however, when republishing is not enabled,
it is not possible to create an infinite loop scenario as the target
does not try to produce additional WAN events.

This commit simply introduces a new method to `WanPublisher` which is
specific for republished replication, and is called from the
`WanPutOperation` which handles forwarded WAN events. This allows us to
skip these cluster name checks if the event is not being republished.

This commit also adds to the javadoc of `WanReplicationRef` to show the
default value of republishing WAN events, and a simple regression test to
validate functionality.

Fixes https://hazelcast.atlassian.net/browse/HZ-4343

GitOrigin-RevId: 4761a525314f9dde0324de647eea2f5e1359a9cf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Source: Internal PR or issue was opened by an employee
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants