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.

Sign up for GitHub

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

Jump to bottom

Broker health check with TopicVersion.V2 failed #13520

Closed
gaozhangmin opened this issue Dec 27, 2021 · 2 comments · Fixed by #13525
Closed

Broker health check with TopicVersion.V2 failed #13520

gaozhangmin opened this issue Dec 27, 2021 · 2 comments · Fixed by #13525
Assignees
@gaozhangmin
Labels
type/bug The PR fixed a bug or issue reported a bug

Comments

@gaozhangmin
Copy link
Contributor

gaozhangmin commented Dec 27, 2021 •
edited
Loading

1、Broker health check failed with TopicVersion.V2 but it's ok with TopicVersion.V1, The failed reason is:

2021-12-27T13:21:17,350+0800 [pulsar-io-4-71] WARN  org.apache.pulsar.client.impl.BinaryProtoLookupService - [persistent://pulsar/hidden-ip:8080/healthcheck] failed to get Partitioned metadata : {"errorMsg":"Policies not found for pulsar/hidden-ip:8080 namespace","reqId":1293596554348340272, "remote":"", "local":""}
org.apache.pulsar.client.api.PulsarClientException$BrokerMetadataException: {"errorMsg":"Policies not found for pulsar/hidden-ip:8080 namespace","reqId":1293596554348340272, "remote":"", "local":""}
        at org.apache.pulsar.client.impl.ClientCnx.getPulsarClientException(ClientCnx.java:1154) ~[org.apache.pulsar-pulsar-client-original-2.10.0-SNAPSHOT.jar:2.10.0-SNAPSHOT]
        at org.apache.pulsar.client.impl.ClientCnx.handlePartitionResponse(ClientCnx.java:607) [org.apache.pulsar-pulsar-client-original-2.10.0-SNAPSHOT.jar:2.10.0-SNAPSHOT]
        at org.apache.pulsar.common.protocol.PulsarDecoder.channelRead(PulsarDecoder.java:130) [org.apache.pulsar-pulsar

Policies not found for namespace pulsar/host:8080 under znode admin/policies.

But Why v1 is successful? v1's healthcheck topic name is global, checkReplication is skipped.

I cannot decide the best solution to fix it.
@gaozhangmin gaozhangmin added the type/bug The PR fixed a bug or issue reported a bug label Dec 27, 2021
@sijie sijie mentioned this issue Dec 27, 2021
Closed
@gaozhangmin gaozhangmin mentioned this issue Dec 27, 2021
Merged
3 tasks
@codelipenghui
Copy link
Contributor

@gaozhangmin Can you reproduce the issue on 2.8.x or 2.9.1? We are enabled health checks for many clusters but never found such an anomaly.

@gaozhangmin
Copy link
Contributor Author

gaozhangmin commented Dec 27, 2021 •
edited
Loading

@gaozhangmin Can you reproduce the issue on 2.8.x or 2.9.1? We are enabled health checks for many clusters but never found such an anomaly.

Yes, i tested with 2.9.1 and master branch. TopicVersion.V1 is ok. but TopicVersion.V2 is failed.

@Technoboy- Technoboy- mentioned this issue Apr 21, 2022
Merged
1 task
codelipenghui pushed a commit that referenced this issue Apr 25, 2022
@Technoboy-
[improve][broker] Tidy up the system topic. (#15252)
aa4df1b 
### Motivation

For #13520, #14643, #14949, we fix some issues related to system topic but result in checking the system topic in different method. So it's better to tidy up the system topic.

So put these system topic names into a new class called SystemTopicNames.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gaozhangmin gaozhangmin

Labels
type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Healthcheck v2 failed gaozhangmin/pulsar
3 participants
@hangc0276 @gaozhangmin @codelipenghui