Describe the bug
kafka-ch-dispatcher logs show "Unsubscribing from channel" messages that shows subscriptions that belong to a different channel. This suggests the dispatcher possibly unsubscribes a different subscription that was meant to be unsubscribed.
Note, the "Unsubscribing from channel" msg here, showing a Subscription 37fe21a9-c642-4f22-b734-89a74f9997db being unsubscribed from {"Namespace":"kafka-stable-kn-retry-2","Name":"channel-0"} , while it was originally subscribed to
kc-broker-stable-dlq-2 broker-0-kne-trigger , which is a different channel in a different namespace.
Expected behavior
No inconsistent logs. Dispatcher should not unsubscribe unrelated channels or subscriptions.
To Reproduce
Steps to reproduce the behavior are unknown at this point, for now this is just something suspicious noticed in the logs. The test used variously configured brokers in several namespaces.
Knative release version
eventing 0.19.2, eventing-kafka 0.19.1
Describe the bug kafka-ch-dispatcher logs show "Unsubscribing from channel" messages that shows subscriptions that belong to a different channel. This suggests the dispatcher possibly unsubscribes a different subscription that was meant to be unsubscribed.
Note, the "Unsubscribing from channel" msg here, showing a Subscription 37fe21a9-c642-4f22-b734-89a74f9997db being unsubscribed from
{"Namespace":"kafka-stable-kn-retry-2","Name":"channel-0"}
, while it was originally subscribed tokc-broker-stable-dlq-2 broker-0-kne-trigger
, which is a different channel in a different namespace.Expected behavior No inconsistent logs. Dispatcher should not unsubscribe unrelated channels or subscriptions.
To Reproduce Steps to reproduce the behavior are unknown at this point, for now this is just something suspicious noticed in the logs. The test used variously configured brokers in several namespaces.
Knative release version eventing 0.19.2, eventing-kafka 0.19.1
Additional context