Skip to content
This repository has been archived by the owner on Dec 11, 2020. It is now read-only.

We should be more aggresive when deleting old traces #30

Open
kikito opened this issue Dec 23, 2014 · 1 comment
Open

We should be more aggresive when deleting old traces #30

kikito opened this issue Dec 23, 2014 · 1 comment
Assignees

Comments

@kikito
Copy link
Contributor

kikito commented Dec 23, 2014

Currently we delete traces based on the number of traces alone.

This might not be enough: a bunch of big traces can consume all the available memory and make the monitor fail - this has caused us trouble with 1 user already. We should be erasing by memory consumption instead of by number. And we could probably remove really old traces (i.e. 1 week old).

@mikz
Copy link
Contributor

mikz commented Jan 5, 2015

Deleting them by time still does not solve the issue. Only way how to do this properly is to count the memory usage. We already have internal ticket about this.

@mikz mikz assigned kikito and unassigned mikz May 19, 2015
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