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

Identify source of StackOverflowErrors in ingest processing #106847

Open
tylerperk opened this issue Mar 27, 2024 · 1 comment
Open

Identify source of StackOverflowErrors in ingest processing #106847

tylerperk opened this issue Mar 27, 2024 · 1 comment
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement Team:Data Management Meta label for data/management team

Comments

@tylerperk
Copy link

Description

We've seen some instances of StackOverflowErrors happening during ingest pipeline processing, likely related to regexp processing in grok or gsub processors. It is currently hard to trace these errors back to a specific pipeline/processor/document. We should somehow make it easier to narrow these down to speed up the troubleshooting.
@tylerperk tylerperk added >enhancement :Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP Team:Data Management Meta label for data/management team labels Mar 27, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Data Management/Ingest Node Execution or management of Ingest Pipelines including GeoIP >enhancement Team:Data Management Meta label for data/management team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@elasticsearchmachine @tylerperk