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] [broker] Producer created by replicator is not displayed in topic stats #20229

Conversation

poorbarcode
Copy link
Contributor

@poorbarcode poorbarcode commented May 5, 2023

Motivation

There is an error Producer with name xxx already exists, but there is no producer in the response of topic stats .

2023-04-25T21:33:02,386+0000 [pulsar-io-4-3] ERROR org.apache.pulsar.client.impl.PartitionedProducerImpl - [persistent://xxx/georeplication_test/georep_test_prod0_to_prod1] Could not create partitioned producer.
2023-04-25T21:33:02,386+0000 [pulsar-io-4-3] ERROR org.apache.pulsar.client.impl.ProducerImpl - [persistent://xxx/georeplication_test/georep_test_prod0_to_prod1-partition-0] [pulsar.repl.event-platform-pulsar-0-sn-->event-platform-pulsar-1-sn] Failed to create producer: {"errorMsg":"org.apache.pulsar.broker.service.BrokerServiceException$NamingException: Producer with name 'pulsar.repl.event-platform-pulsar-0-sn-->event-platform-pulsar-1-sn' is already connected to topic","reqId":1925711601144825936, "remote":"event-platform-1.production.tcc.services/172.18.36.144:6651", "local":"/172.18.9.0:55690"}

A producer of the remote cluster is automatically created when replication is turned on. But we can't see anything about it from the response of (remote cluster) pulsar-admin topic stats

Modifications

Make this producer displayed in the topic stats

Documentation

  • doc
  • doc-required
  • doc-not-needed
  • doc-complete

Matching PR in the forked repository

PR in forked repository:

  • x

@github-actions github-actions bot added the doc-not-needed Your PR changes do not impact docs label May 5, 2023
@gaoran10
Copy link
Contributor

gaoran10 commented May 5, 2023

/pulsarbot rerun-failure-checks

@poorbarcode
Copy link
Contributor Author

/pulsarbot rerun-failure-checks

1 similar comment
@poorbarcode
Copy link
Contributor Author

/pulsarbot rerun-failure-checks

@Technoboy- Technoboy- added this to the 3.1.0 milestone May 6, 2023
@codecov-commenter
Copy link

Codecov Report

Merging #20229 (97da9dd) into master (0dd238a) will increase coverage by 38.45%.
The diff coverage is 100.00%.

Impacted file tree graph

@@              Coverage Diff              @@
##             master   #20229       +/-   ##
=============================================
+ Coverage     34.48%   72.93%   +38.45%     
+ Complexity    12537     3696     -8841     
=============================================
  Files          1614     1868      +254     
  Lines        126170   138592    +12422     
  Branches      13771    15246     +1475     
=============================================
+ Hits          43509   101082    +57573     
+ Misses        77053    29459    -47594     
- Partials       5608     8051     +2443     
Flag Coverage Δ
inttests 24.28% <100.00%> (+0.15%) ⬆️
systests 24.74% <100.00%> (?)
unittests 72.22% <100.00%> (+39.11%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
...sar/broker/service/persistent/PersistentTopic.java 79.23% <100.00%> (+25.58%) ⬆️

... and 1508 files with indirect coverage changes

@congbobo184 congbobo184 merged commit 9f7a539 into apache:master May 6, 2023
poorbarcode added a commit that referenced this pull request May 6, 2023
…ic stats (#20229)

### Motivation

A producer of the remote cluster is automatically created when replication is turned on. But we can't see anything about it from the response of `(remote cluster) pulsar-admin topic stats`

### Modifications

Make this producer displayed in the topic stats

(cherry picked from commit 9f7a539)
poorbarcode added a commit that referenced this pull request May 6, 2023
…ic stats (#20229)

### Motivation

A producer of the remote cluster is automatically created when replication is turned on. But we can't see anything about it from the response of `(remote cluster) pulsar-admin topic stats`

### Modifications

Make this producer displayed in the topic stats

(cherry picked from commit 9f7a539)
poorbarcode added a commit that referenced this pull request May 7, 2023
…ic stats (#20229)

### Motivation

A producer of the remote cluster is automatically created when replication is turned on. But we can't see anything about it from the response of `(remote cluster) pulsar-admin topic stats`

### Modifications

Make this producer displayed in the topic stats

(cherry picked from commit 9f7a539)
nicoloboschi pushed a commit to datastax/pulsar that referenced this pull request May 11, 2023
…ic stats (apache#20229)

### Motivation

A producer of the remote cluster is automatically created when replication is turned on. But we can't see anything about it from the response of `(remote cluster) pulsar-admin topic stats`

### Modifications

Make this producer displayed in the topic stats

(cherry picked from commit 9f7a539)
(cherry picked from commit bf117bb)
@lhotari
Copy link
Member

lhotari commented Apr 5, 2024

This PR introduced something that could be considered a regression. The issue is #22442 . @poorbarcode Please check that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants