独立模式token-server单实例稳定性问题
Open
area/cluster-flow
kind/question
- Dominant language
- Java
- Stars
- 23.1k
- Forks
- 8.1k
- PR merge metrics
- No merged PRs in 30d
Description
### 一、版本信息
Setinel 1.7版本
###
### 二、问题
我们在生产环境使用集群限流,采用token-server为独立模式部署。对于一个服务A,此时只能指定一个token-server,如果服务A的所有接口都配置了限流,那服务A流量都会到这个token-server单实例上,当服务A流量大时候,token-server单点压力也很大。
想咨询下生产环境下使用 token-server 独立模式部署 方案是是什么,怎么避免上面的问题?
Contributor guide
Research direction
Start by reviewing the issue's description of standalone token-server deployment in Sentinel 1.7 and the stated single-instance traffic bottleneck. No source files, tests, or entry points are identified, so first determine where this deployment limitation is documented or implemented. Done would require an agreed production deployment approach that avoids the reported pressure, not just an isolated code edit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100