[
https://issues.apache.org/jira/browse/KAFKA-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eno Thereska updated KAFKA-4199:
--------------------------------
Assignee: (was: Guozhang Wang)
> When a window store segment is dropped we should also clear any corresponding
> cached entries
> --------------------------------------------------------------------------------------------
>
> Key: KAFKA-4199
> URL: https://issues.apache.org/jira/browse/KAFKA-4199
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Affects Versions: 0.10.1.0
> Reporter: Damian Guy
> Priority: Minor
>
> In KIP-63 we introduced a CachingWindowStore, but it currently doesn't have a
> way to be informed when the underlying store drops a segment. In an ideal
> world, when a segment is dropped we'd also remove the corresponding entries
> from the cache.
> Firstly, we need to understand if it is an issue if they don't get dropped.
> They will naturally be evicted when the cache becomes full, but this could
> impact other stores in the thread. i.e., what if any performance impact
> exists?
> If we find there is an unacceptable performance penalty we might need to add
> a callback to the WindowStore API such that we can be notified when segments
> are removed
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
