alibaba/Sentinel

Support LRU evicting mechanism for origin statistic map in StatisticNode

Open

#860 opened on Jun 24, 2019

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Java (8,150 forks)batch import
good first issuekind/feature

Repository metrics

Stars
 (23,109 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Issue Description

Type: feature request

Describe what happened (or what feature you want)

我们的业务场景，希望能能够按照调用方的IP来限流，Sentinel 目前支持按照调用源来限流，但是没有淘汰策略，业务真正使用起来，假如IP数量比较多，风险有点大，所以希望能够支持LRU，业务使用起来更稳定。

其实热点参数限流，目前是支持LRU的，但是为什么不能用热点参数来限流呢？ 热点参数限流，一般情况下，需要把限流的源绑定到参数上，这样才可以使用。但是实际的业务场景很复杂，例如上游服务不愿意改动，所以用热点参数限流可能做起来就不是那么的方便。所以才需要能够按照调用源来限流。例如按IP，这样只需要获取到上游服务的IP就行，并且IP过多的情况下，还支持LRU，就比较稳妥了。

Describe what you expected to happen

How to reproduce it (as minimally and precisely as possible)

Tell us your environment

Anything else we need to know?

Contributor guide

Research direction
Understand the existing hot spot parameter LRU eviction mechanism in Sentinel, then design and implement a similar eviction for the origin statistic map in StatisticNode. Ensure thread safety and performance.
Tech stack
java
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaSentinelFlow Control
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35