-
Notifications
You must be signed in to change notification settings - Fork 4
Handling failed requests #254
Copy link
Copy link
Open
Labels
area: clientEndpoint client, HTTP, transport, ZMQEndpoint client, HTTP, transport, ZMQpriority: P2Medium — address within quarterMedium — address within quartertype: featureNew feature or capabilityNew feature or capability
Metadata
Metadata
Assignees
Labels
area: clientEndpoint client, HTTP, transport, ZMQEndpoint client, HTTP, transport, ZMQpriority: P2Medium — address within quarterMedium — address within quartertype: featureNew feature or capabilityNew feature or capability
When running requests, especially when running under high concurrency, the execution can run into failed requests due to the network. Even running on a single node (both client and server), we can run into port exhaustion.
Ideally we would like to handle those failures to not invalidate the runs. However this imposes a certain policy on the execution which might not agree with the server implementation.