You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Damian Guy (JIRA)" <ji...@apache.org> on 2016/09/20 14:22:21 UTC

[jira] [Created] (KAFKA-4199) When a window store segment is dropped we should also clear any corresponding cached entries

Damian Guy created KAFKA-4199:
---------------------------------

             Summary: 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
            Assignee: Guozhang Wang
            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)