fix: increase SPOE processing timeout from 5s to 30s#96
Merged
oleksandr-nc merged 1 commit intomainfrom Mar 24, 2026
Merged
Conversation
Signed-off-by: Oleksander Piskun <oleksandr2088@icloud.com>
kyteinsky
approved these changes
Mar 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes Flaky test in AppAPI: nextcloud/app_api#783
The SPOE agent and K8s HTTP server share a Python
asyncioevent loop. During heavy K8s operations (deploy, stop, expose), the event loop can be blocked long enough that HAProxy's5sSPOE processing timeout expires before the routing decision is returned.This causes HAProxy to return
503with<NOSRV>because no backend is selected.Increase timeout processing to
30sin both SPOE engine configs. The SPOE handler itself completes in microseconds - the30sheadroom covers event loop contention during concurrent K8s API calls.