Mailing-List: contact jira-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@kafka.apache.org
Date: Wed, 29 Nov 2017 19:28:00 +0000 (UTC)
From: "Matthias J. Sax (JIRA)" <jira@apache.org>
To: jira@kafka.apache.org
Message-ID: <JIRA.13121661.1511965781000.348077.1511983680208@Atlassian.JIRA>
In-Reply-To: <JIRA.13121661.1511965781000@Atlassian.JIRA>
References: <JIRA.13121661.1511965781000@Atlassian.JIRA> <JIRA.13121661.1511965781391@jira-lw-us.apache.org>
Subject: [jira] [Commented] (KAFKA-6282) exactly_once semantics breaks demo
 application
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 29 Nov 2017 19:28:05 -0000


    [ https://issues.apache.org/jira/browse/KAFKA-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16271398#comment-16271398 ] 

Matthias J. Sax commented on KAFKA-6282:
----------------------------------------

Transactions by default require a replication factor of three (for an internally used topic -- not for user topics). Thus, you will need three brokers. Can you try this? Or reconfigure the broker with a different replication factor for the internal topic used to coordinate transactions (config {{transaction.state.log.replication.factor}}).

> 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: 0.11.0.0, 1.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. Streams remain in state REBALANCING, no errors on warning printed. MAIN thread forever blocks waiting TransactionCoordinator response (CountdownLatch.await()) and this message getting printed: [kafka-producer-network-thread | streams-wordcount-client-StreamThread-1-0_0-producer] DEBUG org.apache.kafka.clients.producer.internals.TransactionManager - [Producer clientId=streams-wordcount-client-StreamThread-1-0_0-producer, transactionalId=streams-wordcount-0_0] Enqueuing transactional request (type=FindCoordinatorRequest, coordinatorKey=streams-wordcount-0_0, coordinatorType=TRANSACTION)


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)