Closed jszwedko closed 1 year ago
Since Vector internally uses hyper
as a HTTP client, this lifehack can be used for the timeout implementation: https://github.com/hyperium/hyper/issues/1097#issuecomment-287633760
This is causing long waiting time while stoping vector.
ERROR vector_common::shutdown: Source 'xxx' failed to shutdown before deadline. Forcing shutdown.
ERROR vector::topology::running: Failed to gracefully shut down in time. Killing components. components="xxx, grafana_com_prometheus
The scraping also seems to stop working after the timeout sometimes. I didn't see any data even when the endpoint is back to online.
A note for the community
Problem
If the endpoint that the scrape is hitting is slow to respond, Vector seems to patiently wait. I would have expected there to be a (possibly configurable) HTTP timeout.
Or maybe it should time out using
scrape_interval_secs
?Configuration
Version
vector 0.23.0
Debug Output
Example Data
Test server:
With a dummy file at
./metrics
to serve as the response.Additional Context
No response
References