Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mqtt session takeover is not working when the second client connects to the same Zilla instance #620

Closed
bmaidics opened this issue Dec 5, 2023 · 0 comments · Fixed by #692
Assignees
Labels
bug Something isn't working

Comments

@bmaidics
Copy link
Contributor

bmaidics commented Dec 5, 2023

We're not receiving the reset frame on the group stream -> not leaving the group with the first connection
repro:
start 1 zilla
connect using mosquitto_sub -V '5' -t 'newTopic5' -d -i 'my-client' -p 1883
connect again from a different terminal: mosquitto_sub -V '5' -t 'newTopic5' -d -i 'my-client' -p 1883
First connection should be teared down

Since we connect to the same zilla instance with the same consumer group instanceId, when we connect with the second client the group stream assigns the previous memberId to the JoinGroupRequest (not empty as I think it should be). Kafka realizes, that it's already a member, and that's it. It's already the leader -> we're not leaving the group with the first one.

Added the two pcaps for the first and the second connections.
join_requests.zip

@bmaidics bmaidics added the bug Something isn't working label Dec 5, 2023
@bmaidics bmaidics changed the title Mqtt session takeover is not working when the second client connect to the same Zilla instance Mqtt session takeover is not working when the second client connects to the same Zilla instance Dec 5, 2023
@akrambek akrambek assigned bmaidics and unassigned akrambek Dec 30, 2023
@jfallows jfallows assigned akrambek and unassigned bmaidics Jan 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants