集群限流服务端返回too many request时为什么回退到本地限流模式

[Roronoa-Zoro]

代码如下，既然token server返回too many request了，再回退到本地模式，那么又会有一部分请求能放行，这怎么限流，甚至说当配置的集群限流阈值很大时，这就限制不住吧。
版本：1.8.8
class:FlowRuleChecker,
方法如下:

private static boolean applyTokenResult(/*@NonNull*/ TokenResult result, FlowRule rule, Context context,
                                                         DefaultNode node,
                                                         int acquireCount, boolean prioritized) {
        switch (result.getStatus()) {
            case TokenResultStatus.OK:
                return true;
            case TokenResultStatus.SHOULD_WAIT:
                // Wait for next tick.
                try {
                    Thread.sleep(result.getWaitInMs());
                } catch (InterruptedException e) {
                    e.printStackTrace();
                }
                return true;
            case TokenResultStatus.NO_RULE_EXISTS:
            case TokenResultStatus.BAD_REQUEST:
            case TokenResultStatus.FAIL:
            case TokenResultStatus.TOO_MANY_REQUEST:
                return fallbackToLocalOrPass(rule, context, node, acquireCount, prioritized);
            case TokenResultStatus.BLOCKED:
            default:
                return false;
        }
    }

[LearningGp]

TOO_MANY_REQUESTS indicates that the TokenServer has exceeded its processing capacity, which is distinct from a BLOCKED decision triggered by specific flow rules. In this scenario, fallbackToLocalOrPass is expected behavior. If you wish to maintain limits during such overflows, consider tuning the local threshold accordingly.

[Roronoa-Zoro]

TOO_MANY_REQUESTS indicates that the TokenServer has exceeded its processing capacity, which is distinct from a BLOCKED decision triggered by specific flow rules. In this scenario, fallbackToLocalOrPass is expected behavior. If you wish to maintain limits during such overflows, consider tuning the local threshold accordingly.

right, am refactoring this logic now

[oss-sentinel-ai]

Issue Evaluation

Category: bug | Status: Needs Verification

This issue has been flagged as a potential bug. It requires code-level verification to confirm reproducibility and root cause.

Next steps:

• Code-level verification will be performed to assess validity
• If confirmed, a fix proposal may be generated automatically

---

Automated evaluation by github-manager-bot