Problems / Async and streaming, medium

Logging platform: the indexer falls behind

Services ship 2,000 log batches a second to a log index with 4 vCPUs, and indexing a batch costs 3 ms of CPU.

Solve it in the labTake it as a mock interview

Unlock it once for 15 credits; everything inside it is free (runs, changes, Submit, results, hints). Sign in with Google to start; new accounts get free credits.

Your goals

Success ≥ 99%, p99 ≤ 2 s.

Test cases

Like a coding problem, a solution has to pass every case, not just the one it was built for. Submit in the lab runs all 5; 1 of them are hidden until then.

  1. As given. The problem’s own traffic, scheduled failures and seed.
  2. Peak hour. 25% more traffic than the problem states, with the same failures.
  3. A slow dependency. The main data store or model answers twice as slowly for part of the run.
  4. A server dies. One replica of the service with the most replicas is killed for part of the run.

The traffic

2,000 requests a second for 30 seconds: 100% writes.

The system

What each component does in this design, and what calls it. The simulator mimics each one from these settings.

ComponentIts job hereSettings
Load balancerLoad balancerTraffic enters here.Calls Log ingest.Layer 4 balancers route by IP and port; layer 7 balancers read HTTP and can route by path or header.–
Log ingestApp serviceLoad balancer forwards to it.Calls Log index.Little's law: throughput ≈ concurrency ÷ latency. 200 slots at 50 ms serve about 4,000 req/s.3 replicas × 200 slots · timeout 4.0 s
Log indexSearch indexLog ingest calls it.Search engines build an inverted index: each word points to the documents that contain it.64 slots

More async and streaming problems