You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given a topic with a shared subscription, consumed by different nodes.
How would I proceed to dispose of the topic/subscription (even if the backlog is not empty).
Forcing a topic deletion through the admin-api does not work as the topic and subscription get auto-recreated by the consumers.
This means I have to somehow instruct all the consumers to close before unsubscribing, but then, how to you dispose of the subscription and topic ?
Same thing with forcing unsubscribing via the admin-api, if a consumer is still connected it will recreate the subscription. Thus it also means I have to know when all consumers are closed before trying to unsubscribe.
Otherwise, I can call unsubscribe with the force parameter on each node but it does not feel like a proper solution. That means, each consumer will try to unsubscribe, then each consumer will try to delete the topic using the force parameter also to prevent exception because a consumer is still attached.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Given a topic with a shared subscription, consumed by different nodes.
How would I proceed to dispose of the topic/subscription (even if the backlog is not empty).
Forcing a topic deletion through the admin-api does not work as the topic and subscription get auto-recreated by the consumers.
This means I have to somehow instruct all the consumers to close before unsubscribing, but then, how to you dispose of the subscription and topic ?
Same thing with forcing unsubscribing via the admin-api, if a consumer is still connected it will recreate the subscription. Thus it also means I have to know when all consumers are closed before trying to unsubscribe.
Otherwise, I can call
unsubscribewith theforceparameter on each node but it does not feel like a proper solution. That means, each consumer will try to unsubscribe, then each consumer will try to delete the topic using theforceparameter also to prevent exception because a consumer is still attached.All reactions