-
Notifications
You must be signed in to change notification settings - Fork 335
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
When topic is deleted forced, don't to tigger reconnect logic #623
Comments
And the java demo as follows:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
When topic is deleted forced, under normal circumstances, we should force the producer to be deleted. What the client feels is that the producer has been closed, instead of triggering the logic of reconnection.
Actual behavior
When topic is deleted forced, the request triggers the logic of reconnection.
Steps to reproduce
allowAutoTopicCreation=false
instandalone.conf
topic-1
The same code logic, we can see the following error message in java, this is the behavior we expect:
System configuration
Pulsar version: x.y
The text was updated successfully, but these errors were encountered: