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

escalate plugin: handle origin not reachable #11847

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

bneradt
Copy link
Contributor

@bneradt bneradt commented Nov 6, 2024

Update the escalate plugin to handle dispatching to the failover server if the original server is down.

This also adds a new autest for the escalate plugin.

Fixes: #11836

Update the escalate plugin to handle dispatching to the failover server
if the original server is down.

This also adds a new autest for the escalate plugin.

Fixes: apache#11836
@bneradt bneradt added escalate escalate plugin Redirect labels Nov 6, 2024
@bneradt bneradt added this to the 10.1.0 milestone Nov 6, 2024
@bneradt bneradt self-assigned this Nov 6, 2024
Copy link
Contributor

@shukitchan shukitchan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice. The key is to use the TSHttpTxnServerStateGet is to see we are in trouble with the origin connection.

@bryancall bryancall requested a review from cmcfarlen December 2, 2024 23:18
@bneradt bneradt merged commit ec6fcee into apache:master Dec 12, 2024
15 checks passed
@bneradt bneradt deleted the escalate_for_not_reachable branch December 12, 2024 22:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
escalate escalate plugin Redirect
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When there's no response from the Origin, the escalate plugin does not function correctly.
3 participants