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
@nchaulet, I've added e2e tests for a 429 response (and timeout) from ES when fleet-server initializes, but have not reproduced the crash. Do we know anything else about what caused the issue?
@nchaulet, I've added e2e tests for a 429 response (and timeout) from ES when fleet-server initializes, but have not reproduced the crash. Do we know anything else about what caused the issue?
No other than the logs there was nothing else, (it seems it only happens one time, so we may want to close this and re-open if this happen more frequently)
Description
It seems Fleet server standalone crash during startup if elasticsearch return a 429 (could happen in serverless if the proxy refuse the connetion)
It's probably something we should handle, and recover from.
The text was updated successfully, but these errors were encountered: