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

TBS: processor fails and stops when transaction/span is too large #12053

Closed
simitt opened this issue Nov 15, 2023 · 0 comments · Fixed by #12509
Closed

TBS: processor fails and stops when transaction/span is too large #12053

simitt opened this issue Nov 15, 2023 · 0 comments · Fixed by #12509
Assignees
Labels
Milestone

Comments

@simitt
Copy link
Contributor

simitt commented Nov 15, 2023

APM Server version (apm-server version):
8.10 (and previous)

Description of the problem including expected versus actual behavior:
Under specific circumstances, the apm-server tail sampler process returns and stops without shutting down the apm-server. This seems to happen in relation to tail based sampling when a span cannot be deleted from the local storage due to its size (https://github.com/elastic/apm-server/blob/main/x-pack/apm-server/sampling/processor.go#L536).
This manifests in an error message such as failed to delete span from local storage: Txn is too big to fit into one request.
Right now the only way to mitigate is to manually restart the apm-server.

To fix this we need to

  • already reject events that exceed a max size when they are received, as well as ensuring that events of allowed size can be processed by the system
  • avoid situations where the processor stops running without stopping the apm-server.
@simitt simitt added the bug label Nov 15, 2023
@simitt simitt changed the title TBS: processor fails and stops when span is too large TBS: processor fails and stops when transaction/span is too large Nov 15, 2023
@simitt simitt added this to the 8.13 milestone Jan 4, 2024
@simitt simitt assigned kruskall and unassigned kruskall Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants