Open sshanks-kx opened 8 months ago
Occurs every time .kfk.Metadata[client] called after subscription is made (e.g. call twice, get 2 UNKNOWN_TOPIC_OR_PART msgs). Doesn't occur when called prior to any subscription.
Created librdkafka issue https://github.com/confluentinc/librdkafka/issues/4589 (can see same occurrence without using kdb+).
Current workaround is that if you need to use .kfk.Metadata
to see topics/etc, call it prior to subscription.
Update now on linked issue. May be issue with librdkafka. To try possible fix.
Tested with the pending librdkafka pull request - bug still appears to be there. Informed librdkafka dev. Current workaround is to do any metadata request prior to subscription.
bug doesnt occur with v2.0.2 of librdkafka. will await response from librdkafka devs.
looks like its working again on latest pr change to librdkafka (issue linked above). tested with kdb+. will await future librdkafka release to see if it makes it in.
Fixed in underlying librdkafka 2.4.0
Running
.kfk.Metadata[client];
from consumer can present callback msg as follows:when doing this after doing a subscribe, it can make it look like the subscription had failed (when it hasn't).
Temp removing
.kfk.Metadata[client];
after any subscription, the callback no longer fires with a UNKNOWN_TOPIC_OR_PART. It doesn't appear to stop the subscription from occurring, whether its there or not.Will find out why & change this effect