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] Resource Leak when do health check. #21989

Closed
2 tasks done
thetumbled opened this issue Jan 30, 2024 · 0 comments · Fixed by #21990
Closed
2 tasks done

[Bug] Resource Leak when do health check. #21989

thetumbled opened this issue Jan 30, 2024 · 0 comments · Fixed by #21990

Comments

@thetumbled
Copy link
Member

thetumbled commented Jan 30, 2024

Search before asking

  • I searched in the issues and found nothing similar.

Version

master

Minimal reproduce step

We will do the health check for the cluster by rest api org.apache.pulsar.broker.admin.impl.BrokersBase#healthCheck every 1 min. But recently we meet a case that the health check fail.

bin/pulsar-admin --admin-url http://XXX brokers healthcheck
image

There is no any error log in the broker log, the random message has been produced to the health-check topic, but the reader fail to read it out, so the logic stuck at

org.apache.pulsar.broker.admin.impl.BrokersBase#healthCheckRecursiveReadNext

, which result into the created producers and readers can't be closed, and the scheduled async tasks can't be completed as well, and the number of these objects increase as time goes by.
For example:
bin/pulsar-admin topics stats persistent://pulsar/XXX/healthcheck
image

What did you expect to see?

1

What did you see instead?

1

Anything else?

No response

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@thetumbled thetumbled changed the title [Bug] Memory Leak when do health check. [Bug] Resource Leak when do health check. Jan 30, 2024
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 a pull request may close this issue.

1 participant