[
https://issues.apache.org/jira/browse/KAFKA-5989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax resolved KAFKA-5989.
------------------------------------
Resolution: Duplicate
\cc [~damianguy] It this is not a duplicate, please reopen.
> disableLogging() causes an initialization loop
> ----------------------------------------------
>
> Key: KAFKA-5989
> URL: https://issues.apache.org/jira/browse/KAFKA-5989
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Affects Versions: 0.11.0.1
> Reporter: Tuan Nguyen
> Attachments: App.java
>
>
> Using {{disableLogging()}} for either of the built-in state store types
> causes an initialization loop in the StreamThread.
> Case A - this works just fine:
> {code}
> final StateStoreSupplier testStore = Stores.create(topic)
> .withStringKeys()
> .withStringValues()
> .inMemory()
> // .disableLogging()
> .maxEntries(10)
> .build();
> {code}
> Case B - this does not:
> {code}
> final StateStoreSupplier testStore = Stores.create(topic)
> .withStringKeys()
> .withStringValues()
> .inMemory()
> .disableLogging()
> .maxEntries(10)
> .build();
> {code}
> A brief debugging dive shows that in Case B,
> {{AssignedTasks.allTasksRunning()}} never returns true, because of a remnant
> entry in {{AssignedTasks#restoring}} that never gets properly restored.
> See [^App.java] for a working test (requires ZK + Kafka ensemble, and at
> least one keyed message produced to the "test" topic)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
