CPU throttling observed after using get_enrichment_table_record function in VRL pipeline #24012
Unanswered
andrepbento
asked this question in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We are experiencing CPU throttling issues after updating our VRL implementation to include the get_enrichment_table_record function call in our Vector pipeline. The throttling started immediately after this change.
Details:
We have checked other metrics such as Network RX/TX and Disk IO, but none correlate with the CPU throttling.
The issue only started after switching to the VRL implementation that calls get_enrichment_table_record.
Expected behavior:
No CPU throttling or significant CPU spikes when using the get_enrichment_table_record function.
Additional context:
Increasing the minimum replicas from 3 to 6 helped diluting the ingestion traffic and reduced throttling. Also, increasing the CPU limit per pod to 10 helped, but CPU usage remains very low (<10%) constantly.
Any guidance on how to optimize or debug this further would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions