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.

Sign up for GitHub

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

Jump to bottom

Tracing: limit amount of data stored #3322

Closed
kormat opened this issue Nov 5, 2019 · 5 comments
Closed

Tracing: limit amount of data stored #3322

kormat opened this issue Nov 5, 2019 · 5 comments

Comments

@kormat
Copy link
Contributor

kormat commented Nov 5, 2019

I had 105GB of data in traces/ that i've never used, or knew about. Can we cap the amount of trace data that gets stored on disk? Or, failing that, maybe disable it by default.
@lukedirtwalker
Copy link
Collaborator

We could just delete traces whenever we setup a new topology.

@oncilla
Copy link
Contributor

oncilla commented Apr 15, 2020

partially addressed by #3709

The underlying issue is #1916

@lukedirtwalker
Copy link
Collaborator

@oncilla #1916 seems unrelated? Also #3709 doesn't really improve this, since the data in /traces is a bind-mount and not affected by -v.

@oncilla
Copy link
Contributor

oncilla commented Apr 17, 2020

Uff. I meant to link to jaegertracing/jaeger#1916

It is partially addressed because scion topology deletes the traces dir when starting the topology

@oncilla
Copy link
Contributor

oncilla commented Jun 29, 2021

Not an issue anymore

@oncilla oncilla closed this as completed Jun 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lukedirtwalker @oncilla @kormat