HomeArenaGraphSignalTopics

/ The Arena

Prove your engineering skills.

GLOBAL+50 XP

Implement a Custom Kafka Partitioner with Key-Skew & Hotspot Mitigation

Problem Overview

Standard Murmur2 key hashing maps all events sharing a key to a single partition. When high-volume enterprise tenants generate massive event spikes, that partition suffers catastrophic Partition Skew (Hot-Spotting), causing broker CPU saturation, disk starvation, and consumer lag.

In this landmark capstone, you will implement an enterprise Tenant-Aware Custom Partitioner:

  1. VIP Partition Pool Isolation: Segregate dedicated partitions (0 .. vipCount - 1) exclusively for designated high-volume enterprise tenants.
  2. Hotspot Splaying: Distribute heavy tenant traffic across the VIP partition pool using composite key salting (${key}:${entitySalt}).
  3. Standard Tenant Murmur2 Hashing: Deterministically route standard tenants across remaining partitions (vipCount .. totalPartitions - 1).
  4. Uniform Sticky Partitioner for Unkeyed Records: Route unkeyed (key = null) records with sticky partition affinity.

Join The Arena

Create an account to submit your implementation, test against our containerized CI suite, and climb the global leaderboard.

Create Account

ALREADY HAVE AN ACCOUNT? LOG IN