-
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
Persistent topic is always temporarily unavailable #5284
Comments
is this for a new consumer ? |
both new producer and new consumer, and lasted for a few minutes, restart the broker can resolve. |
We are getting a similar issue from our custom client code when running a load test from 10 concurrent producer processes. In our setup we create a new producer before sending each message, send message, and close producer. We start getting "topic temporarily unavailable" after about 8000 producers / messages were created. This is runs through Pulsar Proxy ->Broker deployed on kubernetes. It seems like Pulsar starts having an issue when too many producers are created over a short period of time. With our load test we are able to reproduce it pretty consistently: Re reproducing:
|
Can you give me a test code? It seems that it is difficult for me to reproduce this problem locally. including some configurations of the cluster. @TC-oKozlov |
Looks like bundle unload/load happened in the middle. |
Same issue for me - seemed to occur during a Topic Unload
UPDATE: FYI I was using Pulsar 2.6.1 |
Same here "Failed to create producer: Topic is temporarily unavailable" , getting this intermittently |
Hi, Is this issue fixed after 2.7.x? |
Hello, we had have the same issue. We could not even delete the topic which was affected by command response:
also reponse for same command after all brokeres were restarted:
On server side was observed
As solution we had to perform removing item from zookeeper by zookeeper shell command and restart all brokers Is there any better workaround for it? |
We had exactly the same issue in 2.7.2. The broker log:
There are no logs shows like |
hi there @codelipenghui, any progress on the issue? we are also blocking on #5284 for our release? |
This PR #11737 Which version you are using? |
Thanks for replying @codelipenghui |
…ding - possible related issues are apache#5284, apache#14941 and apache#20526
…ding - possible related issues are apache#5284, apache#14941 and apache#20526
…ding - possible related issues are apache#5284, apache#14941 and apache#20526
Describe the bug
Here is the error log at broker side:
To Reproduce
Difficult to reproduce
The text was updated successfully, but these errors were encountered: