[
https://issues.apache.org/jira/browse/MINIFICPP-959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896148#comment-16896148
]
Mr TheSegfault edited comment on MINIFICPP-959 at 7/30/19 1:50 PM:
-------------------------------------------------------------------
It should also be noted that if I have my way:
https://issues.apache.org/jira/browse/MINIFICPP-974 we would force PublishKafka
( and many others ) to be removed from the release list without sufficient
tesets.
was (Author: phrocker):
It should also be noted that if I have my way:
https://issues.apache.org/jira/browse/MINIFICPP-974 we would force PublishKafka
( and many others ) to be removed from the release list.
> 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
>
> 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.14#76016)
