Romans Markuns created KAFKA-6282:
-------------------------------------
Summary: exactly_once semantics breaks demo application
Key: KAFKA-6282
URL: https://issues.apache.org/jira/browse/KAFKA-6282
Project: Kafka
Issue Type: Bug
Components: streams
Affects Versions: 1.0.0, 0.11.0.0
Environment: Tested on i7+24GB Ubuntu16.04 and i7+8GB Windows 7, with
cluster 1.0.0 and 0.11.0.0 and streams 1.0.0 and 0.11.0.0
Reporter: Romans Markuns
Attachments: WordCountDemo.java, server.properties
+What I try to achieve+
Do successful run of Kafka streams app with setting "processing.guarantee" set
to "exactly_once"
+How+
Use Kafka quickstart example
(https://kafka.apache.org/10/documentation/streams/quickstart) and modify only
configuration parameters.
Things I've changed:
1) Add one line to WordCountDemo:
{code:java}
props.put(StreamsConfig.PROCESSING_GUARANTEE_CONFIG,
StreamsConfig.EXACTLY_ONCE);
{code}
2) Modify server.properties to be the same as we use in QA: set broker id to 1,
allow deleting topics via admin client and set initial rebalance delay to 3 s.
+What I expect+
Modified demo app works exactly as the original as presented in link above.
+What I get+
1) Original app works fine. Output topic after each line is submitted via
console producer.
2) Modified app does not process topic record after it is submitted via console
producer. Stream is in state RUNNING, no errors on warning printed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
