Skip to content
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

Outlier detection for connections #5751

Open
ikhoon opened this issue Jun 12, 2024 · 0 comments · May be fixed by #5763
Open

Outlier detection for connections #5751

ikhoon opened this issue Jun 12, 2024 · 0 comments · May be fixed by #5763

Comments

@ikhoon
Copy link
Contributor

ikhoon commented Jun 12, 2024

Currently, there is no way to actively detect errors for specific connections and terminate connections that are unhealthy.

It would be useful when a server uses a load balancer as its endpoint. A host-level circuit breaker is not effective when a specific server behind the LB is not operating. If there are two servers and one server does not operate properly, the circuit may become open.

We may provide a OutlierDectionRule, similar to CircuitBreakerRule, to let users decide whether to close the connection if necessary.
https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/outlier

ikhoon added a commit to ikhoon/armeria that referenced this issue Jun 14, 2024
Motivation:

Currently, there is no extension point to detect errors for specific
connections and terminate connections that are unhealthy.

Related: line#5751

Modifications:

- TBU

Result:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant