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][broker] If there is a deadlock in the service, the probe should return a failure because the service may be unavailable #23635

Open
3 tasks done
yyj8 opened this issue Nov 24, 2024 · 0 comments · May be fixed by #23634
Labels
type/bug The PR fixed a bug or issue reported a bug

Comments

@yyj8
Copy link
Contributor

yyj8 commented Nov 24, 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

all version

Minimal reproduce step

Simulate a producer or consumer deadlock and then request /status.html probe.

What did you expect to see?

Probe response failed, and the thread stack was printed for easy troubleshooting, and then the service was triggered to restart.

What did you see instead?

Probe response "ok"

Anything else?

No response

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@yyj8 yyj8 added the type/bug The PR fixed a bug or issue reported a bug label Nov 24, 2024
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
1 participant