[ https://issues.apache.org/jira/browse/KAFKA-4175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493818#comment-15493818 ]
ASF GitHub Bot commented on KAFKA-4175: --------------------------------------- GitHub user dguy opened a pull request: https://github.com/apache/kafka/pull/1862 KAFKA-4175: Can't have StandbyTasks in KafkaStreams where NUM_STREAM_THREADS_CONFIG > 1 standby tasks should be assigned per consumer not per process You can merge this pull request into a Git repository by running: $ git pull https://github.com/dguy/kafka kafka-4175 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/1862.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1862 ---- commit 4e4019f7143f27cf942c69f9eb2942cf4f83c01b Author: Damian Guy <damian....@gmail.com> Date: 2016-09-15T16:14:35Z assign standby tasks per consumer not per process ---- > Can't have StandbyTasks in KafkaStreams where NUM_STREAM_THREADS_CONFIG > 1 > --------------------------------------------------------------------------- > > Key: KAFKA-4175 > URL: https://issues.apache.org/jira/browse/KAFKA-4175 > Project: Kafka > Issue Type: Bug > Components: streams > Affects Versions: 0.10.1.0 > Reporter: Damian Guy > Assignee: Damian Guy > Fix For: 0.10.1.0 > > > When we have StandbyTasks in a Kafka Streams app and we have > 1 threads per > instance we can run into: > {code} > Caused by: java.io.IOException: task [1_0] Failed to lock the state > directory: /private/tmp/kafka-streams-smoketest/2/SmokeTest/1_0 > {code} > This is because the same StandbyTask has been assigned to each thread in the > same KafkaStreams instance -- This message was sent by Atlassian JIRA (v6.3.4#6332)