You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 2, 2024. It is now read-only.
Problem
The solution that was proposed in #182 did not fix the problem of adding the subscriptions to the channel only when the corresponding consumer in the dispatcher is ready and due to a lag in Sarama between the consumer group creation and starting the consumer, it seems there's no other way than to propagate the consumer readiness from the dispatcher
Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.
devguyio
changed the title
[consolidated] Update channel's status.subscriber based on the dispatcher propagated consumer readiness
[consolidated] Update channel's status.subscribers based on the dispatcher propagated consumer readiness
Dec 16, 2020
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.
Problem
The solution that was proposed in #182 did not fix the problem of adding the subscriptions to the channel only when the corresponding consumer in the dispatcher is ready and due to a lag in Sarama between the consumer group creation and starting the consumer, it seems there's no other way than to propagate the consumer readiness from the dispatcher
Exit Criteria
A measurable (binary) test that would indicate that the problem has been resolved.
Time Estimate (optional):
3d
Additional context (optional)
#134
#98
knative/eventing-contrib#1556
#182
The text was updated successfully, but these errors were encountered: