Skip to content

Add support for Healthchecking Dynamic Backends#635

Open
camilee03 wants to merge 3 commits into
mainfrom
camilee03/add-dynamic-backend-healthcheck-hostcalls
Open

Add support for Healthchecking Dynamic Backends#635
camilee03 wants to merge 3 commits into
mainfrom
camilee03/add-dynamic-backend-healthcheck-hostcalls

Conversation

@camilee03

Copy link
Copy Markdown
Member

Meant to support the changes made in this PR in the Rust SDK to support healthchecking hostcalls for dynamic backends

There is additional healthchecking-related terminology like here, which sets backend health to BackendHealth::Unknown (which the static backend sets as a config). This should be fine to leave as is.

@camilee03 camilee03 added the feature-prod Related to matching the production C@E environment label Jun 10, 2026
@dgryski

dgryski commented Jun 10, 2026

Copy link
Copy Markdown
Member

Does this prevent sending http requests to unhealthy backends too?

@camilee03

camilee03 commented Jun 10, 2026

Copy link
Copy Markdown
Member Author

@dgryski No, it doesn't. This is focused on adding healthchecks as an option to dynamic backends on creation re the work in ExecuteD along similar lines, not on the other side of when a user tries to query a created backend and healthcheck it.

Unless I've misinterpreted the code for Viceroy, and it's different from ExecuteD, I believe that functionality shouldn't ~need to be changed because once the dynamic backend is built, it is processed the same way as a static backend (lmk if that assumption is incorrect)?

@dgryski

dgryski commented Jun 10, 2026

Copy link
Copy Markdown
Member

When backend health was added to viceroy, the status was not checked during an http send. So, no change then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature-prod Related to matching the production C@E environment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants