Maciej Mensfeld
Maciej Mensfeld
> As ruby-kafka is multithread safe it makes sense to have one instance of async producer per process. Just keep in mind that historically ruby-kafka producer had a lot of...
@2rba you mind providing benchmarks? in regards to the cache, I have a plan to improve it in the upcoming months by aligning it with the librdkafka metadata refresh layer...
O nice! So now the main thing would be to get rid of the partition key sync refresh to prevent clogging.
@technicalpickles aside from help command (and sub-help for topics) all others do require the presence of karafka.rb and need to be context aware. I'm not sure if this provides enough...
@brandonzylstra I cannot review it without the CLA :(
Wait until this issue is resolved / answered not to cause issues to the end users: https://github.com/confluentinc/librdkafka/issues/4870
closing. We jump over due to regressions and head to 2.6.1
duplicated by https://github.com/karafka/karafka/issues/2606 - moving reasoning here.
Things we need to do to make this happen: - [ ] Fix segfaults related to oauth bearear callback assignments - [ ] Ignore fork specs for jruby - [...
@headius, the thing is, other callbacks work as expected, so I think it's rather a misuse/misconfiguration. I'll get back to you next week when I look into this with more...