You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/05/03 18:55:04 UTC
[jira] [Commented] (KAFKA-4996) Fix findbugs multithreaded
correctness warnings for streams
[ https://issues.apache.org/jira/browse/KAFKA-4996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995430#comment-15995430 ]
ASF GitHub Bot commented on KAFKA-4996:
---------------------------------------
GitHub user amitdaga opened a pull request:
https://github.com/apache/kafka/pull/2966
KAFKA-4996: Fix findbugs multithreaded correctness warnings for streams
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/amitdaga/kafka findbugs-streams-multithread
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/2966.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 #2966
----
commit bf7c4cf3588112e8d9518b43ed086aa36588d75f
Author: Amit Daga <ad...@adobe.com>
Date: 2017-04-30T17:58:39Z
Fixing multithread correctness warning in streams
----
> Fix findbugs multithreaded correctness warnings for streams
> -----------------------------------------------------------
>
> Key: KAFKA-4996
> URL: https://issues.apache.org/jira/browse/KAFKA-4996
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: Colin P. McCabe
> Labels: newbie
>
> Fix findbugs multithreaded correctness warnings for streams
> {code}
> Multithreaded correctness Warnings
>
> Code Warning
> AT Sequence of calls to java.util.concurrent.ConcurrentHashMap may not be atomic in org.apache.kafka.streams.state.internals.Segments.getOrCreateSegment(long, ProcessorContext)
> IS Inconsistent synchronization of org.apache.kafka.streams.KafkaStreams.stateListener; locked 66% of time
> IS Inconsistent synchronization of org.apache.kafka.streams.processor.internals.StreamThread.stateListener; locked 66% of time
> IS Inconsistent synchronization of org.apache.kafka.streams.processor.TopologyBuilder.applicationId; locked 50% of time
> IS Inconsistent synchronization of org.apache.kafka.streams.state.internals.CachingKeyValueStore.context; locked 66% of time
> IS Inconsistent synchronization of org.apache.kafka.streams.state.internals.CachingWindowStore.cache; locked 60% of time
> IS Inconsistent synchronization of org.apache.kafka.streams.state.internals.CachingWindowStore.context; locked 66% of time
> IS Inconsistent synchronization of org.apache.kafka.streams.state.internals.CachingWindowStore.name; locked 60% of time
> IS Inconsistent synchronization of org.apache.kafka.streams.state.internals.CachingWindowStore.serdes; locked 70% of time
> IS Inconsistent synchronization of org.apache.kafka.streams.state.internals.RocksDBStore.db; locked 63% of time
> IS Inconsistent synchronization of org.apache.kafka.streams.state.internals.RocksDBStore.serdes; locked 76% of time
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)