stackabletech / stackabletech/trino-lb
trinolb keeps hanging when api server is not available
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 37
- Forks
- 8
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 1
Description
tonight we had some issues with the kubeapi server (not available because network issue for ~1-2 min) which is used by trinolb to fetch health state of connected trino clusters (CRs). it seems like there is no timeout / retry configured for that type of request, which leads to trinolb waiting forever (30 min in our case, then i restarted the sts manually) to get an answer of the api server.
important to know may be that were using stackable autoscaler
is there a timeout set for kubeapi server calls?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing trinolb's kubeapi server requests used to fetch health state for connected Trino clusters (CRs), including the path used with the Stackable autoscaler. Reproduce an unavailable-server case and determine the expected timeout or retry behavior; done means trinolb no longer waits indefinitely when the kubeapi server is unreachable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100