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

[Bug] "Topic does not have schema to check" on topic-level geo replication #22608

Open
2 of 3 tasks
shulaoh opened this issue Apr 28, 2024 · 2 comments
Open
2 of 3 tasks
Labels
type/bug The PR fixed a bug or issue reported a bug

Comments

@shulaoh
Copy link

shulaoh commented Apr 28, 2024

Search before asking

  • I searched in the issues and found nothing similar.

Read release policy

  • I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

Version

pulsar 3.0.1
jdk 8

Minimal reproduce step

  1. create 2 clusters with local zk.
  2. create tenant, namespace, topic on each cluster.
  3. pulsar-admin topics set-replication-clusters --clusters cluster-A,cluster-B to setup topic-level geo replication
  4. create consumer with Schema.STRING.
    client.newConsumer(Schema.STRING).consumerName("a1")
    .subscriptionName("ca1")
    .topic("persistent://aa/bb/cc")
    .replicateSubscriptionState(true)
    .messageListener((c, m) -> {
    System.out.println("message: " + m.getValue());
    try {
    c.acknowledge(m);
    } catch (ClientException e) {
    throw new RuntimeException(e);
    }
    }).subscribe();

What did you expect to see?

consumer can be registered succesfully.

What did you see instead?

Topic does not have schema to check

Anything else?

btw, namespace-level geo replication works well.

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@shulaoh shulaoh added the type/bug The PR fixed a bug or issue reported a bug label Apr 28, 2024
@danielnaumau
Copy link

I'm facing the same problem, is there any progress here?

@dao-jun
Copy link
Member

dao-jun commented May 21, 2024

#22720 could fix this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Development

No branches or pull requests

3 participants