Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Problem
We're using vector with many source-transform-sink blocks (hundreds of them). I've noticed that config changes works well on-the-fly, but if the change is too big, vector might die (vectordev-a-1 exited with code 139).
It happens when the number of source-transform-sink blocks changes by 200 or so (each reading from kafka, writing to S3).
So say you have 300 such blocks, and you delete 200 of them and let Vector reload the configuration file, it will most probably die.
A note for the community
Problem
We're using vector with many source-transform-sink blocks (hundreds of them). I've noticed that config changes works well on-the-fly, but if the change is too big, vector might die (
vectordev-a-1 exited with code 139
). It happens when the number of source-transform-sink blocks changes by 200 or so (each reading from kafka, writing to S3). So say you have 300 such blocks, and you delete 200 of them and let Vector reload the configuration file, it will most probably die.Configuration
Version
0.25.1
Debug Output
No response
Example Data
The processed data is comprised of json strings
Additional Context
No response
References
No response