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
Eureka client uses thread pool schedulers to schedule tasks:
Fetch registry
Heartbeats
This assumes that every scheduled task finishes either with success or error. If this assumption is broken, no new tasks (for the same type) gets scheduled.
In some scenarios we have seen inside AWS that the socket read timeouts do not get triggered which makes the thread reading HTTP response stuck and hence break the above assumption.
The client should be able to identify this scenario and be resilient.
The text was updated successfully, but these errors were encountered:
Eureka client uses thread pool schedulers to schedule tasks:
This assumes that every scheduled task finishes either with success or error. If this assumption is broken, no new tasks (for the same type) gets scheduled.
In some scenarios we have seen inside AWS that the socket read timeouts do not get triggered which makes the thread reading HTTP response stuck and hence break the above assumption.
The client should be able to identify this scenario and be resilient.
The text was updated successfully, but these errors were encountered: