<p>How can I configure istio for such case:</p>
<p>There is <code>serviceentry</code> with 10 external ip addresses. Two among them are broken.</p>
<p>I have configured circuit breaker, but don't quite sure is it possible to automatically resend request if it was failed on broken endpoint.  Or it just removes this endpoint from connection pool, returning failure to application?</p>

Belenot
<p>There are two fields under <a href="https://istio.io/latest/docs/reference/config/networking/destination-rule/#TrafficPolicy" rel="nofollow noreferrer">TrafficPolicy</a> which are relevant to circuit breaking: <a href="https://istio.io/latest/docs/reference/config/networking/destination-rule/#ConnectionPoolSettings" rel="nofollow noreferrer">ConnectionPoolSettings</a> and <a href="https://istio.io/latest/docs/reference/config/networking/destination-rule/#OutlierDetection" rel="nofollow noreferrer">OutlierDetectionIn</a></p>
<p><code>ConnectionPoolSettings</code>, the volume of connections can be configured for a service.</p>
<p><code>OutlierDetection</code> is for controlling the eviction of unhealthy services from the load balancing pool.</p>
<p>So the endpoint is removed till the circuit becomes <code>closed</code> again and the service will be allowed to handle requests again. You can't resend a request and don't need to because after a threshold when circuit comes in <code>closed</code> state requests will sent to that service automatically.</p>
