You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@rocketmq.apache.org by "laohu (JIRA)" <ji...@apache.org> on 2017/12/29 04:07:02 UTC
[jira] [Commented] (ROCKETMQ-348) Got much exception when master
restart after power cut
[ https://issues.apache.org/jira/browse/ROCKETMQ-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16305957#comment-16305957 ]
laohu commented on ROCKETMQ-348:
--------------------------------
Please provide boot exception.thanks
> Got much exception when master restart after power cut
> ------------------------------------------------------
>
> Key: ROCKETMQ-348
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-348
> Project: Apache RocketMQ
> Issue Type: Bug
> Affects Versions: 4.2.0
> Reporter: lusong
> Assignee: vongosling
>
> We use m-s mq cluster, and master's config is
> "brokerRole=SYNC_MASTER
> flushDiskType=ASYNC_FLUSH" .
> Rmq version is 3.2.6. I guess this issue is also exist in apache rmq.
> One day master's server was power cut , then we fixed the os and restarted master broker. We found master always generate this exception "findMapedFileByOffset offset not matched, request Offset: 19382879484, index: -7, mapedFileSize: 1073741824, mapedFiles count: 2, StackTrace: \n\tjava.lang.Thread.getStackTrace(Thread.java:1567)\n\tcom.alibaba.rocketmq.common.UtilAll.currentStackTrace(UtilAll.java:59)\n\tcom.alibaba.rocketmq.store.MapedFileQueue.findMapedFileByOffset(MapedFileQueue.java:467)\n\tcom.alibaba.rocketmq.store.CommitLog.getMessage(CommitLog.java:664)\n\tcom.alibaba.rocketmq.store.DefaultMessageStore.getMessage(DefaultMessageStore.java:546)\n\tcom.alibaba.rocketmq.broker.processor.PullMessageProcessor.processRequest(PullMessageProcessor.java:283)".
> It generated 21G data in storeerror.log in 20 minutes and the server's load was very high.
> Is this a bug and how to resolve this problem?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)