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

add advertised listenerName for geo-replicator #10751

Merged
merged 2 commits into from
Jun 2, 2021

Conversation

wangjialing218
Copy link
Contributor

Motivation

In case of geo-replicator, if replicator client can't connect to remote cluster unless using advertised listener, currently there is no way to set advertised listener for replicator.

Modifications

Add listenerName to ClusterData.
When creating replicator producer for remote cluster, use listenerName if exists.
Add admin cli command to set listenerName for remote cluster.

@eolivelli eolivelli requested review from codelipenghui and sijie and removed request for codelipenghui May 31, 2021 10:33
Copy link
Member

@zymap zymap left a comment

Choose a reason for hiding this comment

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

LGTM. Could you please resolve the conflicts?

@codelipenghui codelipenghui merged commit 38d037c into apache:master Jun 2, 2021
yangl pushed a commit to yangl/pulsar that referenced this pull request Jun 23, 2021
### Motivation

In case of geo-replicator, if replicator client can't connect to remote cluster unless using advertised listener, currently there is no way to set advertised listener for replicator.

### Modifications

Add listenerName to ClusterData.
When creating replicator producer for remote cluster, use listenerName if exists.
Add admin cli command to set listenerName for remote cluster.
sijie pushed a commit that referenced this pull request Jul 14, 2021
### Motivation

fix mistake when resolve the conflicts in #10751
codelipenghui pushed a commit that referenced this pull request Jul 23, 2021
### Motivation

fix mistake when resolve the conflicts in #10751

(cherry picked from commit 47b3495)
bharanic-dev pushed a commit to bharanic-dev/pulsar that referenced this pull request Mar 18, 2022
### Motivation

In case of geo-replicator, if replicator client can't connect to remote cluster unless using advertised listener, currently there is no way to set advertised listener for replicator.

### Modifications

Add listenerName to ClusterData.
When creating replicator producer for remote cluster, use listenerName if exists.
Add admin cli command to set listenerName for remote cluster.
bharanic-dev pushed a commit to bharanic-dev/pulsar that referenced this pull request Mar 18, 2022
### Motivation

fix mistake when resolve the conflicts in apache#10751
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants