多集群时member集群经常显示未就绪
- Dominant language
- Go
- Stars
- 98
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
主集群节点上的tower pod报错如下，网络均没有任何问题，但是经常出现，等待2分钟左右又恢复了，
E0115 01:46:14.038945 1 upgradeaware.go:367] Error proxying data from client to backend: read tcp 10.233.78.199:16614->10.233.78.138:48506: read: connection reset by peer
E0115 01:46:14.040117 1 upgradeaware.go:367] Error proxying data from client to backend: read tcp 10.233.78.199:16614->10.233.78.138:48472: read: connection reset by peer
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the upgradeaware.go:367 log entry in the tower pod and inspect how proxy connections relate to member-cluster readiness. Reproduce the intermittent multi-cluster failure, then verify that the member cluster remains ready without the reported connection-reset errors.
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
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100