[
https://issues.apache.org/jira/browse/KAFKA-4492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Damian Guy updated KAFKA-4492:
------------------------------
Description:
This follows on from https://issues.apache.org/jira/browse/KAFKA-4311
The exception seems to be triggered by topologies with multiple joined tables.
As a new record arrives in one table it triggers an eviction. The eviction
causes a flush which will trigger a join processor. These in-turn does a cache
lookup and if the value is not in the cache, then it will be retrieved from the
store and put in the cache, triggering another eviction. And so on.
Exception reported on mailing list
https://gist.github.com/mfenniak/509fb82dfcfda79a21cfc1b07dafa89c
Further investigation into this also reveals that this same eviction process
can send the cache eviction into an infinite loop. It seems that the LRU is
broken.
was:
This follows on from https://issues.apache.org/jira/browse/KAFKA-4311
The exception seems to be triggered by topologies with multiple joined tables.
As a new record arrives in one table it triggers an eviction. The eviction
causes a flush which will trigger a join processor. These in-turn does a cache
lookup and if the value is not in the cache, then it will be retrieved from the
store and put in the cache, triggering another eviction. And so on.
Exception reported on mailing list
https://gist.github.com/mfenniak/509fb82dfcfda79a21cfc1b07dafa89c
> java.lang.IllegalStateException: Attempting to put a clean entry for key...
> into NamedCache
> -------------------------------------------------------------------------------------------
>
> Key: KAFKA-4492
> URL: https://issues.apache.org/jira/browse/KAFKA-4492
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 0.10.1.0
> Reporter: Damian Guy
> Assignee: Damian Guy
> Fix For: 0.10.2.0
>
>
> This follows on from https://issues.apache.org/jira/browse/KAFKA-4311
> The exception seems to be triggered by topologies with multiple joined
> tables. As a new record arrives in one table it triggers an eviction. The
> eviction causes a flush which will trigger a join processor. These in-turn
> does a cache lookup and if the value is not in the cache, then it will be
> retrieved from the store and put in the cache, triggering another eviction.
> And so on.
> Exception reported on mailing list
> https://gist.github.com/mfenniak/509fb82dfcfda79a21cfc1b07dafa89c
> Further investigation into this also reveals that this same eviction process
> can send the cache eviction into an infinite loop. It seems that the LRU is
> broken.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
