https://github.com/Blizzard/node-rdkafka/issues/5 will need to be fixed before we deploy event streams using node-rdkafka to production.
This bug manifests itself after calling consumer.disconnect(). The consumer instances will hang because of lingering rdkakfa objects hanging around and not being freed.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | Xqt | T125197 Give hint to the current socketIO_client in ImportError of rcstream.py | |||
| Declined | None | T91393 RCStream is not accessible from python client due to using socket-io 1.0 while only socket-io 0.9 is offered | |||
| Declined | None | T68232 Upgrade RCStream backend to use socket.io 1.0 protocol | |||
| Resolved | Ottomata | T130651 EventStreams | |||
| Resolved | Ottomata | T148470 Kafka SSE Prototype | |||
| Resolved | Ottomata | T148779 Prepare eventstreams (with KafkaSSE) for deployment | |||
| Resolved | Ottomata | T143925 Productionize and deploy Public EventStreams | |||
| Declined | Ottomata | T148043 Fix consumer.disconnect() node-rdkafka bug |
This was fixed upstream, yeehaw! We'll need to wait until they release a new version to use it for deployment, but ja.