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

[Bug] When the client tps is high, trace messages will be lost #8429

Closed
3 tasks done
LetLetMe opened this issue Jul 23, 2024 · 0 comments · Fixed by #8430
Closed
3 tasks done

[Bug] When the client tps is high, trace messages will be lost #8429

LetLetMe opened this issue Jul 23, 2024 · 0 comments · Fixed by #8430

Comments

@LetLetMe
Copy link
Contributor

Before Creating the Bug Report

  • I found a bug, not just asking a question, which should be created in GitHub Discussions.

  • I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

  • I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

all

RocketMQ version

all

JDK Version

all

Describe the Bug

当客户端消息生成或者消费tps较高时,轨迹消息batch量会比较大,由于之前没限制batch size,当batch size太大时候会出现轨迹消息概率性丢失
When the TPS (Transactions Per Second) of client message generation or consumption is high, the batch size of trajectory messages can become quite large. Due to the lack of a batch size limit previously, when the batch size becomes too large, there is a probabilistic loss of trajectory messages.

Steps to Reproduce

  1. 限制batch siez

  2. 部分重构客户端发送轨迹消息的逻辑

  3. Limit batch size

  4. Partially refactor the client's logic for sending trajectory messages

What Did You Expect to See?

nothing

What Did You See Instead?

nothing

Additional Context

No response

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

Successfully merging a pull request may close this issue.

1 participant