Trafficcontroller keeps connections open after slow consumers events
MasslessParticle opened this issue · comments
Thanks for your submission!
Here are some guidance for submitting your issue.
Tell us why you are submitting?
- I found a bug - here are some steps to recreate it.
- I have an idea for a new feature - please document as "As a user, I would
like to..." - I am having trouble getting setup, understanding documentation, or using
Loggregator in some way - please highlight any resources you are using. - This is an architecture change that will result in cleaner more efficient
code - Tell us why you think this is a good idea.
Steps to reproduce:
- use a
slow_consumer
available inloggregator-tools
with a read interval of 10 seconds - Observe the
slow_consumer
event from trafficcontroller - The
slow_consumer
continues to read messages
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/163097049
The labels on this github issue will be updated when the story is started.
We've announced the deprecation of the TrafficController. Users should subscribe to the RLP or RLP-gateway instead and use it's metrics.