You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
statistics, schedule: stop republishing metrics for a known-tombstoned store
Pick the pure Prometheus-metric-leak subset of tikv#11166 (still open on
master) onto this branch, on top of tikv#11127's backport:
- ObserveHotStat / ResetStoreStatistics / Reset(): stop
storeStatusGauge from being republished by an in-flight
StoreHeartbeat after bury, clean up placementStatusGauge, reset
StoreLimitGauge on a full leader-election reset.
- collectHotMetrics: gate hasHotLeader/hasHotPeer on a single
IsRemoved() read so a tombstoned store's stale HotPeerCache data
can't republish hotSpotStatusGauge between HotPeerCache.gc() ticks.
- SetStoreLimit: reject setting a limit on an already-tombstoned
store, closing the only other write path that could re-add a
cleared StoreLimitGauge/config entry.
- summaryPendingInfluence: re-check each store fresh through the
cluster instead of trusting the possibly-stale StoreSummaryInfo
snapshot before writing HotPendingSum.
Left out (not applicable to this branch): tikv#11166's evict_slow_store.go
/ adjustNetworkSlowStore guards (network-slow-store eviction doesn't
exist here) and its memory-leak-only fixes (region rule fit cache,
storesOfRegion reverse index, StoreHistoryLoads GC), which are a
separate concern from metric leakage and tracked separately.
Signed-off-by: bufferflies <1045931706@qq.com>
0 commit comments