Lianet Magrans created KAFKA-21478:
--------------------------------------

             Summary: Improve consumer membership mgr handling of unexpected 
error in HB response
                 Key: KAFKA-21478
                 URL: https://issues.apache.org/jira/browse/KAFKA-21478
             Project: Kafka
          Issue Type: Task
          Components: clients
            Reporter: Lianet Magrans
            Assignee: Lianet Magrans


The async consumer handles HB responses in a callback. If the logic inside the 
callback throws (unexpected, but could happen with GC side bugs), the exception 
is lost in the client and things left inconsistent (new epoch taken but many 
other steps that follow a HB reponse may not). So the member remains in a 
no-fatal state (heartbeating, so probably looking good to the GC)

This became evident with a GC side bug on KS (KAFKA-20981), that sent an 
unknown status code in a Streams HB response. That bug is fixed but this ticket 
is to improve the client-side handling for such scenarios (the consumer should 
handle the unexpeted, make the client transtion to the existing fatal state 
probably, error bubbled up in poll...like other HB response paths already do 
under "fatal").

This callaback logic 
[https://github.com/apache/kafka/blob/503f9fef61f0590b2f1267f97f42e6217943e842/clients/src/main/java/org/apache/kafka/clients/consumer/internals/AbstractHeartbeatRequestManager.java#L321-L327]
 (to check same for the streams manager, fix consistently in both)



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to