Details
-
Sub-task
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
None
Description
The heartbeat request builder should make sure that all fields are sent in the heartbeat request when the consumer rejoins (currently the HeartbeatRequestManager request builder is reset on failure scenarios, which should cover the fence+rejoin sequence).
Note that the existing HeartbeatRequestManagerTest.testHeartbeatState misses this exact case given that it does explicitly change the subscription when it gets fenced. We should ensure we test a consumer that keeps it same initial subscription when it rejoins after being fenced.
Attachments
Issue Links
- links to