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

Compactors Have a Memory Leak #216

Closed
joe-elliott opened this issue Oct 9, 2020 · 2 comments · Fixed by #950
Closed

Compactors Have a Memory Leak #216

joe-elliott opened this issue Oct 9, 2020 · 2 comments · Fixed by #950
Assignees
@mdisibio

Comments

@joe-elliott
Copy link
Member

joe-elliott commented Oct 9, 2020 •
edited
Loading

Occasionally compactor memory blows up and OOMs:

image

Compactors come back online quickly and tend to recover so the system continues working, but we still need to address. I believe this related to very large traces (100k+ spans) going through the CombineTraces method.
@mdisibio mdisibio mentioned this issue Nov 12, 2020
Merged
3 tasks
@joe-elliott joe-elliott mentioned this issue Aug 26, 2021
Merged
@joe-elliott
Copy link
Member Author

The saga continues. #915 is a temporary band aid to reduce memory usage that does not impact throughput. After this is fixed please undo that change.

@joe-elliott joe-elliott mentioned this issue Sep 13, 2021
Merged
3 tasks
@mdisibio mdisibio mentioned this issue Sep 13, 2021
Merged
3 tasks
@mdisibio
Copy link
Contributor

We determined that this was fixed by #806. (Does not require search to be enabled)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mdisibio mdisibio

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Tempo Changelog Cleanup joe-elliott/tempo
2 participants
@joe-elliott @mdisibio