Page History

...

1. Memory Waste: Stale indexes accumulate indefinitely, consuming heap memory that cannot be reclaimed. In the leadership change and read-from-replica scenarios described above, brokers retain indexes for partitions they no longer serve, leading to:

     - Heap utilization: Grows unbounded over time (observed: 5GB → 12GB over 7 days)
     - GC pressure: Increased full GC frequency as heap fills
     - OOM risk: Eventually requires manual broker restart to clear cache

2. Reduced Cache Effectiveness: When stale entries occupy cache space, active indexes are evicted prematurely, reducing cache hit rates and increasing remote storage API calls.

...