Details
-
Bug
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
2.5.0
-
None
-
None
Description
During soak testing in preparation for the 2.5.0 release, we have discovered a case in which Streams appears to stop making progress. Specifically, this is a failure-resilience test in which we inject network faults separating the instances from the brokers roughly every twenty minutes.
On 2.4, Streams would obviously spend a lot of time rebalancing under this scenario, but would still make progress. However, on the current 2.5 branch, Streams effectively stops making progress except rarely.
This appears to be a severe regression, so I'm filing this ticket as a 2.5.0 release blocker.
Attachments
Issue Links
- links to