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

Unexpected back-check of transaction message in RocketMQ 5.0 #6107

Closed
mz0113 opened this issue Feb 18, 2023 · 5 comments
Closed

Unexpected back-check of transaction message in RocketMQ 5.0 #6107

mz0113 opened this issue Feb 18, 2023 · 5 comments

Comments

@mz0113
Copy link

mz0113 commented Feb 18, 2023

d0489fe9cfc93f6e723c59c0db726979

问题描述:
1.发送端发送事务消息后,等待broker发起回查 , 然后broker于1分钟左右正常发起回查,应用给与事务已提交的响应,broker也收到了这个响应,见上图。但是broker依然发起下一次回查 , 最终查了15次后消息被回滚掉了。但是看下来不是必现,概率大概10%左右会失败。一部分消息是回查了七八次以后成功了,有的查了15次失败了。问题发生有一天内多次发生。
2. 目前mq用的是开源版本,容器化部署,一主一从 。使用cotroller模式进行主从切换。 主从异步刷盘同步复制。但是看了服务器日志,主从切换未发生过,服务运行一直都正常。

最新进展:
3. 目前确认是启用堆外缓存导致的问题,关掉就正常了。好奇堆外缓存看代码是间隔200ms就会提交一次到fileChannel,怎么还会有这个问题呢。。

@RongtongJin RongtongJin changed the title v5.0.0 事务消息发起多次回查,即便应用已经响应可以提交消息 Unexpected back-check of transaction message in RocketMQ 5.0 Feb 19, 2023
@RongtongJin
Copy link
Contributor

#5722 修复了controller模式下与开启堆外内存不兼容的问题,建议后续升级到5.1.0版本。但从你的描述上来看,事务消息的回查似乎与该修复无关。

@fuyou001
Copy link
Contributor

fuyou001 commented Mar 1, 2023

@Focus-rth

@Focus-rth
Copy link
Contributor

  1. 尝试一段时间未复现,可以给下完整的transaction.log?

Copy link

github-actions bot commented Mar 2, 2024

This issue is stale because it has been open for 365 days with no activity. It will be closed in 3 days if no further activity occurs.

@github-actions github-actions bot added the stale label Mar 2, 2024
Copy link

github-actions bot commented Mar 5, 2024

This issue was closed because it has been inactive for 3 days since being marked as stale.

@github-actions github-actions bot closed this as completed Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants