You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@rocketmq.apache.org by 我看好你哦 <fl...@qq.com.INVALID> on 2021/07/16 07:51:20 UTC

consulting [offset not matched] problem

Dear:


1. Please describe the issue you observed:


In the storemirror.log file, there is always an error message that offset does not match. It outputs a log every second. Cause our server disk alarm.How can we solve the problem of not letting log








2. Please tell us about your environment:


jdk:1.8
RocketMQ Version:3.5.8
Cluster configuration: three masters and three slaves



3. Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):


&nbsp;WARN WriteSocketService - findMapedFileByOffset offset not matched, request Offset: 56706266126, index: 525, mapedFileSize: 1073741824, mapedFiles count: 1, StackTrace:
&nbsp; &nbsp; java.lang.Thread.getStackTrace(Thread.java:1589)
&nbsp; &nbsp; com.alibaba.rocketmq.common.UtilAll.currentStackTrace(UtilAll.java:63)
&nbsp; &nbsp; com.alibaba.rocketmq.store.MapedFileQueue.findMapedFileByOffset(MapedFileQueue.java:467)
&nbsp; &nbsp; com.alibaba.rocketmq.store.CommitLog.getData(CommitLog.java:156)
&nbsp; &nbsp; com.alibaba.rocketmq.store.CommitLog.getData(CommitLog.java:150)
&nbsp; &nbsp; com.alibaba.rocketmq.store.DefaultMessageStore.getCommitLogData(DefaultMessageStore.java:818)
&nbsp; &nbsp; com.alibaba.rocketmq.store.ha.HAConnection$WriteSocketService.run(HAConnection.java:334)
&nbsp; &nbsp; java.lang.Thread.run(Thread.java:745)

&nbsp;