temporalio / temporalio/temporal
When temporal k8s pod restart, healer still probe the old pod ip ?
Open
Nobody has claimed this yet.
potential-bug
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Actual Behavior
DiscoverProvider: statichosts.New(hostPorts...)
We found logs in gateway. When fronted pod restart, but temporal-worker still keep visiting old fronted pod IP.
Steps to Reproduce the Problem
- restart fronted pod
- capture package from temporal-worker
Specifications
- Version: v.1.23
- Platform: k8s
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 in common/membership/ringpop/monitor.go at line 204, where DiscoverProvider uses statichosts.New(hostPorts...). Reproduce the issue by restarting the fronted pod and capture traffic from temporal-worker; done means the worker stops contacting the old pod IP after restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100