[jira] [Assigned] (KAFKA-9349) Investigate new member timeout for dynamic v4 JoinGroup

["Jason Gustafson (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-9349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gustafson reassigned KAFKA-9349:
--------------------------------------

    Assignee:     (was: Jason Gustafson)

> Investigate new member timeout for dynamic v4 JoinGroup
> -------------------------------------------------------
>
>                 Key: KAFKA-9349
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9349
>             Project: Kafka
>          Issue Type: Bug
>          Components: core
>            Reporter: A. Sophie Blee-Goldman
>            Priority: Major
>
> While working on KAFKA-9232 I found the timeout behavior to be a bit odd for dynamic members following the v4+ JoinGroup protocol (ie requireMemberId = true). I haven't confirmed that there is a bug, but we couldn't confirm that there definitely isn't so I'm opening this ticket for further investigation:
> During a dynamic join group, the first Join (with {{UNKNOWN_MEMBER_ID}} ) schedules a heartbeat based on session timeout. During the second Join, when memberId is now known, we schedule the heartbeat based on the {{NewMemberTimeout}} — but right above that is a comment that says
> The session timeout does not affect new members since they do not have their memberId and cannot send heartbeats.
> which seems to imply we shouldn’t be scheduling this sessionTimeout-based heartbeat during the first Join. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)