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
I'm curious how Adaptive Request Concurrency works in combination with retries and sinks that support multiple endpoints (e.g. elasticsearch). In particular, how would each of the following configurations affect ARC?
1 endpoint that points to a single IP address (likely a load balancer)
1 endpoint that points to many IP addresses (multiple A records)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Question
I'm curious how Adaptive Request Concurrency works in combination with retries and sinks that support multiple
endpoints(e.g.elasticsearch). In particular, how would each of the following configurations affect ARC?Arecords)It would be nice if the behaviour was documented but all I was able to find was this, which doesn't really cover what I'm after: https://vector.dev/blog/adaptive-request-concurrency/
Vector Config
No response
Vector Logs
No response
Beta Was this translation helpful? Give feedback.
All reactions