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

[RIP-64] Heartbeat Optimization #6720

Closed
zk-drizzle opened this issue May 8, 2023 · 0 comments · Fixed by #6724
Closed

[RIP-64] Heartbeat Optimization #6720

zk-drizzle opened this issue May 8, 2023 · 0 comments · Fixed by #6724

Comments

@zk-drizzle
Copy link
Contributor

zk-drizzle commented May 8, 2023

Is Your Feature Request Related to a Problem?

Currently, heartbeat data is sent by the client to tell the broker that the client is working, and in previous versions, the data for each heartbeat included the complete subscription data. If every consumerGroup has the same subscription and does not change so that the data transmission and calculation have certain redundancy.

Describe the Solution You'd Like

Refer RIP-64

1.Heartbeat detection and subscription data transmission can be separated at a lower cost.
2.Keep the original logic function unchanged after heartbeat optimization.
Chinese version:

Describe Alternatives You've Considered

--

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant