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
I have confirmed that this should be classified as an enhancement rather than a bug/feature.
Summary
When deploying with Kubernetes, changes in broker IP cause the persistAllConsumerOffset process to take excessively long, blocking the updateTopicRouteInfoFromNameServer scheduling task. This requires a restart of the client to immediately restore normal functionality.
Motivation
schedule Executor is single
Each loop requires a 2-second timeout, which means it takes 2 seconds for one queue. For 30 queues, it would take one minute.
Logging for analytics tracking or instrumentation
Describe the Solution You'd Like
Add IP circuit breaker enhancement
Describe Alternatives You've Considered
none
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Before Creating the Enhancement Request
Summary
When deploying with Kubernetes, changes in broker IP cause the
persistAllConsumerOffset
process to take excessively long, blocking theupdateTopicRouteInfoFromNameServer
scheduling task. This requires a restart of the client to immediately restore normal functionality.Motivation
Logging for analytics tracking or instrumentation
Describe the Solution You'd Like
Add IP circuit breaker enhancement
Describe Alternatives You've Considered
none
Additional Context
No response
The text was updated successfully, but these errors were encountered: