[
https://issues.apache.org/jira/browse/MINIFICPP-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Bakai updated MINIFICPP-959:
-----------------------------------
Description:
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).
was:
I don't think librdkafka is doing what it supposed the 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).
> 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
> Priority: Major
>
> 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
(v7.6.3#76005)
