You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Nghia Le (Jira)" <ji...@apache.org> on 2019/09/11 11:03:00 UTC
[jira] [Resolved] (MINIFICPP-959) Review librdkafka thread safety
[ https://issues.apache.org/jira/browse/MINIFICPP-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nghia Le resolved MINIFICPP-959.
--------------------------------
Resolution: Fixed
> Review librdkafka thread safety
> -------------------------------
>
> Key: MINIFICPP-959
> URL: https://issues.apache.org/jira/browse/MINIFICPP-959
> Project: Apache NiFi MiNiFi C++
> Issue Type: Bug
> Reporter: Daniel Bakai
> Assignee: Nghia Le
> Priority: Major
> Time Spent: 2h
> Remaining Estimate: 0h
>
> I don't think librdkafka is doing what it is supposed to around the KafkaLease and the atomic spinlock combined with mutexes.
> It is thread safe in a way that resources are only accessed by one thread at a time, but the behaviour otherwise is I think not what was intended (multiple threads can initialize a KafkaConnection after each other, for example).
--
This message was sent by Atlassian Jira
(v8.3.2#803003)