Skip to content
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

'bucket' notion is unacceptable for log streaming #5

Closed
blt opened this issue Jun 7, 2016 · 0 comments
Closed

'bucket' notion is unacceptable for log streaming #5

blt opened this issue Jun 7, 2016 · 0 comments

Comments

@blt
Copy link
Collaborator

blt commented Jun 7, 2016

The 'bucket' data store present in cernan is acceptable for statsd multiplexing but breaks down as soon as you want to retain datapoints. Which, you do if you pump in graphite or logs.

@blt blt added this to the 0.2.0 - great fire milestone Jun 7, 2016
@blt blt removed the enhancement label Jun 7, 2016
@blt blt closed this as completed Jul 6, 2016
blt pushed a commit that referenced this issue Jan 11, 2017
We noticed that there was something fishy going on with graphite.
In particular, the number of lines push to the programmable_filter
grew _way_ too quickly for the inputs. It turns out, that fancy
line buffer we pass in to avoid allocing small strings repeatedly
was not being cleared and so everything that came in would be
appended there.

This commit also includes the work done as a part of
postmates/hopper:#5 by updating to 0.1.2. All messages will be
delivered in order--as they should have been--and hopper is now
quite a bit faster to boot as it can keep cramming in low-memory
when there's space.

Signed-off-by: Brian L. Troutwine <blt@postmates.com>
blt added a commit that referenced this issue Jan 11, 2017
We noticed that there was something fishy going on with graphite.
In particular, the number of lines push to the programmable_filter
grew _way_ too quickly for the inputs. It turns out, that fancy
line buffer we pass in to avoid allocing small strings repeatedly
was not being cleared and so everything that came in would be
appended there.

This commit also includes the work done as a part of
postmates/hopper:#5 by updating to 0.1.2. All messages will be
delivered in order--as they should have been--and hopper is now
quite a bit faster to boot as it can keep cramming in low-memory
when there's space.

Signed-off-by: Brian L. Troutwine <blt@postmates.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant