envoyproxy/xds-relay

Handle potential thundering herd problem on cache evict

Open

#71 opened on Apr 25, 2020

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Go (29 forks)auto 404
help wanted

Repository metrics

Stars
 (135 stars)
PR merge metrics
 (PR metrics pending)

Description

On cache evict, orchestrator currently closes upstream and all downstream watches for the key that's getting evicted. This could be problematic if there's a lot of downstream connections for the same aggregated key. This will cause a "thundering herd" problem where all downstreams attempt to re-establish a connection with xds-relay. We need to evaluate how to handle this.

Contributor guide

Research direction
Evaluate strategies to mitigate thundering herd during cache eviction, such as jitter, staggered reconnection, or lazy reconnection.
Tech stack
go
Domain
backendapi
Issue type
Research
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoDistributed SystemsCaching
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40