You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
限制batch siez
部分重构客户端发送轨迹消息的逻辑
Limit batch size
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
The text was updated successfully, but these errors were encountered:
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
限制batch siez
部分重构客户端发送轨迹消息的逻辑
Limit batch size
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
The text was updated successfully, but these errors were encountered: