-
Notifications
You must be signed in to change notification settings - Fork 525
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[sourcemaps] support multiple fleet addresses #5514
Comments
Is there any benefit to round-robining the requests vs just selecting a random address to send the request to? I'm guessing selecting a random address would be simpler to implement. |
@estolfo random selection sounds good to me, and I don't think there's any benefit to round robin. @stuartnelson3 do you have any concerns with that? |
No concerns from me |
@axw your comment here suggests that any artifact can be fetched from any fleet server. So why would we need a map of |
@estolfo we don't need to map all of those things to every fleet server address, as they're indeed orthogonal. Does your question stem from the way the code is structured here? apm-server/sourcemap/fleet_store.go Lines 77 to 86 in aeafd43
What we need is:
The |
Yes, I understood we had to keep the |
The current sourcemap fetching code for fleet assumes that we receive only a single fleet server.
Add support for round-robin requests between the fleet servers. Assume all fleet servers are in the same cluster, ie. an artifact is available on each individual server.
Original comment:
#5410 (comment)
The text was updated successfully, but these errors were encountered: