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] subscription of topic in a permanent fence state and consumerList remain offline consumer #20576

Closed
2 tasks done
TakaHiR07 opened this issue Jun 14, 2023 · 4 comments
Labels
Stale type/bug The PR fixed a bug or issue reported a bug

Comments

@TakaHiR07
Copy link
Contributor

TakaHiR07 commented Jun 14, 2023

Search before asking

  • I searched in the issues and found nothing similar.

Version

server version: 2.9.3

Minimal reproduce step

I found the similar problem as #14970 and #19692 and #15051 in our 2.9.3 production environment.

It remain offline consumers in consumerList, but it was removed from the consumerSet and consumers. And this subscription become fenced permanently.

But it is different from #19692. The topic of this subscription is not closed, and this topic has other available subscriptions, only 1 subscription remain offline consumers and become fenced permanently.

企业微信截图_76807075-f79d-4501-962e-10efbcc18f5b

I have encounter this problem twice. I guess this maybe a new possibility for duplicated consumer problem happen.

What did you expect to see?

..

What did you see instead?

..

Anything else?

..

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@TakaHiR07 TakaHiR07 added the type/bug The PR fixed a bug or issue reported a bug label Jun 14, 2023
@poorbarcode
Copy link
Contributor

What is the impact on the user? The new consumers can't be created due to the subscription is not OK, right?

@TakaHiR07
Copy link
Contributor Author

What is the impact on the user? The new consumers can't be created due to the subscription is not OK, right?

Yes. If client restart, it can not consume.

@github-actions
Copy link

The issue had no activity for 30 days, mark with Stale label.

@github-actions github-actions bot added the Stale label Jul 17, 2023
@TakaHiR07
Copy link
Contributor Author

#22283 has fixed the same problem. Close it

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

Successfully merging a pull request may close this issue.

2 participants