Change Details

We're currently running the latest version of python-kafka packaged for Debian, 1.4.3, which we seem to have backported ourselves to Stretch. We have seemingly hit a serious deadlock bug that version of python-kafka has, on the coal service: https://github.com/dpkp/kafka-python/issues/1590 It's possible that the other services we run that rely on that library would be vulnerable to that bug, if they are using consumer groups. Looking at Puppet, it seems like the following services rely on that library and will need to be watched during the upgrade: [x] coal [x] navtiming [x] statsv - eventlogging - hadoop

We're currently running the latest version of python-kafka packaged for Debian, 1.4.3, which we seem to have backported ourselves to Stretch. We have seemingly hit a serious deadlock bug that version of python-kafka has, on the coal service: https://github.com/dpkp/kafka-python/issues/1590 It's possible that the other services we run that rely on that library would be vulnerable to that bug, if they are using consumer groups. Looking at Puppet, it seems like the following services rely on that library and will need to be watched during the upgrade: [x] coal [x] navtiming [x] statsv [x] eventlogging [x] hadoop

We're currently running the latest version of python-kafka packaged for Debian, 1.4.3, which we seem to have backported ourselves to Stretch. We have seemingly hit a serious deadlock bug that version of python-kafka has, on the coal service: https://github.com/dpkp/kafka-python/issues/1590 It's possible that the other services we run that rely on that library would be vulnerable to that bug, if they are using consumer groups. Looking at Puppet, it seems like the following services rely on that library and will need to be watched during the upgrade: [x] coal [x] navtiming [x] statsv -[x] eventlogging -[x] hadoop