-
Notifications
You must be signed in to change notification settings - Fork 15
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
[SOL-76960] Binder does not cleanup flows if flow is opened but binding creation fails #146
Comments
Ping @Mrc0113 |
Yeah, this is a bug. It's failing to cleanup the flows if there's a failure during binding creation after the flow is opened, but before binding creation is complete. Like in this case, when it fails to add subscriptions after the flow is opened.
Not entirely sure if binding creation should be captured by the health indicator (probably yes, but need to verify). If so, then this should be handled by #145 instead of this issue.
Binding creation retries is entirely controlled by the Spring Cloud Stream framework by spring.cloud.stream.bindingRetryInterval. If you want it to "give up", you should configure that to be |
If the queue is already existing but the user is not allowed to consume the queue.
I get an error like this:
What so far is totally ok.
Now the binder is trying this in a endless loop without releasing the failed Flows.
What should be changed:
The text was updated successfully, but these errors were encountered: