You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 are using Vector (v.0.37.0 of helm chart running in gke) to fetch events from a pubsub topic to an elasticsearch (running inside a gke cluster) sink. Problem here is that our pubsub topic only receives messages when a CloudRun instance runs, which is not always and not necessarily at fixed times and it seems that Vector stops retrying to process events from this source if the queue is empty for a while. I know I might be able to get around this problem by changing the retention time on the topic and scheduling restarts to the vector pod but that is the costly option. Ideally vector would constantly retry connecting to this source every x minutes in case new messages were added to the queue.
A note for the community
Problem
We are using Vector (v.0.37.0 of helm chart running in gke) to fetch events from a pubsub topic to an elasticsearch (running inside a gke cluster) sink. Problem here is that our pubsub topic only receives messages when a CloudRun instance runs, which is not always and not necessarily at fixed times and it seems that Vector stops retrying to process events from this source if the queue is empty for a while. I know I might be able to get around this problem by changing the retention time on the topic and scheduling restarts to the vector pod but that is the costly option. Ideally vector would constantly retry connecting to this source every x minutes in case new messages were added to the queue.
Configuration
Version
CHART: vector-0.32.0 APP VERSION: 0.37.0-distroless-libc
Debug Output
No response
Example Data
No response
Additional Context
No response
References
No response
The text was updated successfully, but these errors were encountered: