Skip to content
This repository has been archived by the owner on Sep 19, 2019. It is now read-only.

Bus Cleanup on Exit #3

Open
skrusty opened this issue Jan 13, 2015 · 1 comment
Open

Bus Cleanup on Exit #3

skrusty opened this issue Jan 13, 2015 · 1 comment

Comments

@skrusty
Copy link

skrusty commented Jan 13, 2015

Currently, when the proxy is shutdown, there's no cleanup of queues still active/open.

@blitzrage
Copy link
Contributor

@skrusty so thinking through this, I don't think having this close the topics/queues on proxy shut down actually makes sense, and let me explain why.

So in the future we will likely want to have the ability to let a proxy hand off existing control of the various topics/queues to another proxy. This may be as simple as load balancing, or perhaps you want to upgrade an existing proxy in a container and hand off the existing things to that proxy.

Additionally, if you are closing down a proxy, it's still possible that the information the proxy put on the topics/queues is still relevant and useful for the running applications, which could continue to parse and operate without the proxy in the background.

With that being said, adding some methods to the AppInstance in the go-ari-library does make sense (e.g. StopConsumer, StopProducer) in order to allow a graceful close of the topics/queues. So with those methods being available, the closure of the topics/queues would actually be deferred to the application layer, and not the proxy layer.

This of course doesn't help you too much since you're writing in .NET, however I think this thought process was useful, and will result in some code on the go-ari-proxy for closure of the topics on application close or shutdown in the future.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants