[
https://issues.apache.org/jira/browse/KAFKA-8970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16944828#comment-16944828
]
Nishkam Ravi commented on KAFKA-8970:
-------------------------------------
[~bchen225242] Just want to make sure we are on the same page. If we don't want
two streams to share the same state dir, we could add a check in StateDirectory
initialization and throw an exception when that happens? Or append a randomly
generated suffix to the dir name? This Jira is pointing out a thread-safety
issue that is somewhat different.
> StateDirectory creation fails with Exception
> --------------------------------------------
>
> Key: KAFKA-8970
> URL: https://issues.apache.org/jira/browse/KAFKA-8970
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Nishkam Ravi
> Priority: Major
>
> When two threads try to create KafkaStreams simultaneously, one of them
> succeeds while the other fails with the following exception:
> org.apache.kafka.streams.errors.StreamsException:
> org.apache.kafka.streams.errors.ProcessorStateException: base state directory
> [/tmp/kafka-streams] doesn't exist and couldn't be created
> Quick investigation suggests that this is because the code at/around:
> [https://github.com/apache/kafka/blob/trunk/streams/src/main/java/org/apache/kafka/streams/processor/internals/StateDirectory.java#L82]
> is not synchronized and can lead to race conditions.
> Specifying different values for state.dir can be a workaround for this issue
> but a bit cumbersome. Can we just make this synchronized?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
