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] Deadlock found in branch-3.0 #24034

Open
2 of 3 tasks
dao-jun opened this issue Feb 27, 2025 · 7 comments
Open
2 of 3 tasks

[Bug] Deadlock found in branch-3.0 #24034

dao-jun opened this issue Feb 27, 2025 · 7 comments
Labels
type/bug The PR fixed a bug or issue reported a bug

Comments

@dao-jun
Copy link
Member

dao-jun commented Feb 27, 2025

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

build from branch-3.0

Minimal reproduce step

NONE

What did you expect to see?

No deadlock

What did you see instead?

Have a deadlock

Anything else?

Image

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@dao-jun dao-jun added the type/bug The PR fixed a bug or issue reported a bug label Feb 27, 2025
@dao-jun
Copy link
Member Author

dao-jun commented Feb 27, 2025

maybe need to cherrypick #20697 to branch3.0

@lhotari
Copy link
Member

lhotari commented Feb 28, 2025

maybe need to cherrypick #20697 to branch3.0

Good point. I'll add the label release/3.0.11.

@lhotari
Copy link
Member

lhotari commented Feb 28, 2025

@dao-jun looks like #20984 is also required besides #20697.

@lhotari
Copy link
Member

lhotari commented Feb 28, 2025

@dao-jun I can handle the cherry-picking. Already on it. Looks like #21465 also causes a conflict in resolving the merge conflicts. Just ensuring that I don't reverse that change accidentially when cherry-picking. This is a good example where cherry-picking should have been performed in dependent order.

@lhotari
Copy link
Member

lhotari commented Feb 28, 2025

PR to backport the fixes: #24037

@dao-jun
Copy link
Member Author

dao-jun commented Mar 1, 2025

@lhotari thanks for your work!

@lhotari
Copy link
Member

lhotari commented Mar 1, 2025

@lhotari thanks for your work!

@dao-jun tests are failing. One reason is that branch-3.0 is broken, reported as #24038 . The PR #24037 changes also introduce a new test failure.

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

2 participants