mittwald / mittwald/kube-httpcache
Port 8090 hangs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 313
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
Description
I am able to reproduce very strange scenario.
I have statefulset with 2 varnish pods. I'm sending in a loop purge requests to port 8090 to first Varnish pod. First varnish is properly broadcasting request to second Varnish pod.
While purge requests are flowing, I'm deleting 2nd Varnish pod. First Varnish pod discovers it and removes 1 frontend from the list. I'm repeating this delete 2-3 times in a row.
After few seconds first Varnish node is not accepting calls on port 8090 anymore - cache purge request and curl on port 8090 hangs (from another pod and also from first Varnish pod). I can still connect on port 8080.
Situation never recovers at this point of time and first Varnish is not printing any logs during this time.
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
Reproduce the issue with two Varnish pods by sending repeated purge requests to port 8090 while deleting the peer pod multiple times. Compare the behavior of ports 8090 and 8080 and inspect the first pod's logs; done means port 8090 continues accepting requests after peer removal and the failure is diagnosable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- distributed-systems, infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100