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
When resetting a subscription we must do this via the runners which have a claim on each partition for the consumer group. We do not have a way currently for calling each runner within a deployment. Instead it currently calls the endpoint for the deployment which will reach only one runner.
The text was updated successfully, but these errors were encountered:
Another use case is eg. ensuring all runners have a consistent view of secrets/configs, which has been a problem in the past. Is this the same problem/use case? Figure it out.
When resetting a subscription we must do this via the runners which have a claim on each partition for the consumer group. We do not have a way currently for calling each runner within a deployment. Instead it currently calls the endpoint for the deployment which will reach only one runner.
The text was updated successfully, but these errors were encountered: