On 12/1/16, 9:41 AM, "Joshua Harlow" <harlo...@fastmail.com> wrote:
>Keen, Joe wrote:
>> I¹ll look into testing the newest version of kafka-python and see if it
>> meets our needs. If it still isn¹t stable and performant enough what
>> the available options?
>Fix the kafka-python library or fix monasca; those seem to be the
>options to me :)
>I'd also not like to block the rest of the world (from using newer
>versions of kafka-python) during this as well. But then this may
>diverge/expand into a discussion we had a few summits ago, about getting
>rid of co-instability...
Unfortunately there’s nothing wrong on the Monasca side so far as we know.
We test new versions of the kafka-python library outside of Monasca
before we bother to try integrating a new version. Since 1.0 the
kafka-python library has suffered from crashes and memory leaks severe
enough that we’ve never attempted using it in Monasca itself. We reported
the bugs we found to the kafka-python project but they were closed once
they released a new version.
OpenStack Development Mailing List (not for usage questions)