集群限流 token server 重启+client 退化时会瞬间超时
Open
area/cluster-flow
wait-for-feedback
- Dominant language
- Java
- Stars
- 23.1k
- Forks
- 8.1k
- PR merge metrics
- No merged PRs in 30d
Description
当 master 节点发布重启的时候，client 节点会因为找不到 master 降级为单机限流，但是我们发现线上在这个瞬间部分请求就会出现超时的现象，这个有什么方法可以避免，所以我们现在的操作都是在发布之前先主动将集群限流切换至单机限流，再发布完后切回集群限流，但是这样就比较麻烦，有什么好的思路解决这个问题呢？
Contributor guide
Research direction
No files, tests, or entry points are identified in the issue. Start by tracing the cluster token server restart path and the client’s fallback to standalone rate limiting, then determine how to prevent transient request timeouts and validate the behavior during a restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100