[
https://issues.apache.org/jira/browse/IOTDB-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411866#comment-17411866
]
lisijia commented on IOTDB-1619:
--------------------------------
fine, after scanning code, i find that this issue may have three bugs.
first, raft log files are sorted after recover, it might cause a confusing log
index
second, if there are some logs have not applied when we start cluster,
commitManager can not process these logs, as you see 'missing log entry...'
third,transport client of meta group may not be established.
let's fix it one by one.
> There is an error msg when I restart iotdb-cluster
> --------------------------------------------------
>
> Key: IOTDB-1619
> URL: https://issues.apache.org/jira/browse/IOTDB-1619
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Cluster
> Reporter: FengQingxin
> Priority: Major
> Labels: pull-request-available
> Attachments: image-2021-09-03-17-36-27-985.png
>
>
> Hi
> I met a error msg when I try to restart an iotdb-cluster[3
> nodes，default_replica_num=2] .
> First I restarted the cluster,and try to insert data to it.
> Second using "stop-node.sh" to stop it.
> Third reboot server. Then using "start-node.sh" to restart it.
> At this time , I met the error msg"2021-09-03 16:33:05,237 [main] ERROR
> o.a.i.c.l.m.CommittedEntryManager:252 - missing log entry [last: -1, append
> at: 5397176]"
> !image-2021-09-03-17-36-27-985.png!
> Please check this.
> Thanks.
> B.R.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
