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
feat(exporter/loadbalancing/dnsresolver): add quarantine mechanism for unhealthy endpoints
- Added a quarantine feature for unhealthy endpoints, delaying retries to those endpoints after a configurable period (default: 30s).
- Quarantine settings are configurable via the DNS resolver's `quarantine` section.
- The load balancer will avoid sending data to endpoints marked as unhealthy until their quarantine period expires, using healthy endpoints in the hash ring without triggering unnecessary ring updates.
- This increases resilience by reducing the risk of exporters being stuck in degraded states with repeated failed attempts.
- This feature currently applies only to the DNS resolver.
Refs #43644
# Use this changelog template to create an entry for release notes.
2
+
3
+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4
+
change_type: enhancement
5
+
6
+
# The name of the component, or a single word describing the area of concern, (e.g. receiver/filelog)
7
+
component: exporter/loadbalancing
8
+
9
+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10
+
note: Quarantine mechanism for unhealthy endpoints in the DNS resolver.
11
+
12
+
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13
+
issues: [43644]
14
+
15
+
# (Optional) One or more lines of additional information to render under the primary note.
16
+
# These lines will be padded with 2 spaces and then inserted directly into the document.
17
+
# Use pipe (|) for multiline entries.
18
+
subtext: |
19
+
- Added a quarantine feature for unhealthy endpoints, delaying retries to those endpoints after a configurable period (default: 30s).
20
+
- Quarantine settings are configurable via the DNS resolver's `quarantine` section.
21
+
- The load balancer will avoid sending data to endpoints marked as unhealthy until their quarantine period expires, using healthy endpoints in the hash ring without triggering unnecessary ring updates.
22
+
- This increases resilience by reducing the risk of exporters being stuck in degraded states with repeated failed attempts.
23
+
- This feature currently applies only to the DNS resolver.
24
+
25
+
# If your change doesn't affect end users or the exported elements of any package,
26
+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
27
+
# Optional: The change log or logs in which this entry should be included.
28
+
# e.g. '[user]' or '[user, api]'
29
+
# Include 'user' if the change is relevant to end users.
30
+
# Include 'api' if there is a change to a library API.
Copy file name to clipboardExpand all lines: exporter/loadbalancingexporter/README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,6 +95,9 @@ Refer to [config.yaml](./testdata/config.yaml) for detailed examples on using th
95
95
*`port` port to be used for exporting the traces to the IP addresses resolved from `hostname`. If `port` is not specified, the default port 4317 is used.
96
96
*`interval` resolver interval in go-Duration format, e.g. `5s`, `1d`, `30m`. If not specified, `5s` will be used.
97
97
*`timeout` resolver timeout in go-Duration format, e.g. `5s`, `1d`, `30m`. If not specified, `1s` will be used.
98
+
*`quarantine` node: enables a quarantine mechanism that prevents the exporter from sending data to endpoints that have previously failed (i.e., are marked as unhealthy) until a defined quarantine period passes. While an endpoint is quarantined, only healthy endpoints in the hash ring are used to dispatch data, avoiding unnecessary hash ring updates and reducing the risk of repeatedly targeting unhealthy endpoints.
99
+
*`enabled` toggle to activate endpoint quarantine logic. Default is `false`.
100
+
*`duration` how long in go-Duration format an unhealthy endpoint should remain in quarantine before the exporter retries it (e.g., `30s`, `1m`). Defaults to `30s` if not specified.
98
101
* The `k8s` node accepts the following optional properties:
99
102
*`service` Kubernetes service to resolve, e.g. `lb-svc.lb-ns`. If no namespace is specified, an attempt will be made to infer the namespace for this collector, and if this fails it will fall back to the `default` namespace.
100
103
*`ports` port to be used for exporting the traces to the addresses resolved from `service`. If `ports` is not specified, the default port 4317 is used. When multiple ports are specified, two backends are added to the load balancer as if they were at different pods.
0 commit comments