-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Topic is already fenced #15451
Comments
@youg9203 Looks like we have some system topic that state is |
Thanks, I'm looking forward |
The issue had no activity for 30 days, mark with Stale label. |
I also met this issue. I am deleting a partition of a topic, it is not system topic. here is error log
|
The issue had no activity for 30 days, mark with Stale label. |
Yes,still exists...
|
Yes,still exists... |
@mattisonchao Sorry, I'm not working on Pulsar anymore but it looks like the issue still exists and the community is still facing the problem. |
I meet the problem when I use pulsar-manage to create a partitioned topic, I add a subscription failed, then I want to delete the topic , the error has occurred :
pulsar broker version: 3.2.1 |
yes
Faed?
***@***.***
…------------------ 原始邮件 ------------------
发件人: "Yougeshwar ***@***.***>;
发送时间: 2024年9月12日(星期四) 晚上9:15
收件人: ***@***.***>;
抄送: ***@***.***>; ***@***.***>;
主题: Re: [apache/pulsar] Topic is already fenced (Issue #15451)
I'm sorry for missing the message, is the problem still exist? @youg9203 @yapxue
@mattisonchao Sorry, I'm not working on Pulsar anymore but it looks like the issue still exists and the community is still facing the problem.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
I used the get partitionedTopicList API, and the result returned is as follows: persistent://tenant/namespace/topic-test-1 ; As you can see, it has lost the partition theme 0 of the index;
|
Describe the bug
The force delete tenant is causing an error on topic deletion.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Whether either topic is closed or deleted, it should not block the deletion, the tenant should be deleted.
Console error log
Desktop (please complete the following information):
Additional context
Pulsar version: 2.9.2
Pulsar Helm chart: 2.9.2
JWT Auth enabled: true
Few more config enabled at broker:
The text was updated successfully, but these errors were encountered: