Skip to content

adding loadShed outcome #2359

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

Merged
merged 2 commits into from
Jul 9, 2024
Merged

adding loadShed outcome #2359

merged 2 commits into from
Jul 9, 2024

Conversation

mikea
Copy link
Contributor

@mikea mikea commented Jul 5, 2024

loadShed means the server didn't start processing the request. It could happen when server is overloaded or in some other not-very-healthy state.

Not used anywhere yet, the plan is to use for load-shedding experiments. There's downstream change open updating the master copy.

Unavailable means the server didn't start processing the request. It could happen when server is overloaded or in some other not-very-healthy state.
@mikea mikea requested review from a team as code owners July 5, 2024 19:25
@mikea mikea changed the title adding unavailable outcome adding loadShed outcome Jul 9, 2024
@mikea
Copy link
Contributor Author

mikea commented Jul 9, 2024

renamed to loadShed per @kentonv feedback.

@mikea mikea merged commit 6bbc3fe into main Jul 9, 2024
9 checks passed
@mikea mikea deleted the mikea-patch-2 branch July 9, 2024 19:52
ns476 pushed a commit to ns476/workerd that referenced this pull request Aug 2, 2024
loadShed means the server didn't start processing the request. It could happen when server is overloaded or in some other not-very-healthy state.

Not used anywhere yet, the plan is to use for load-shedding experiments. There's downstream change open updating the master copy.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants