中学继续回滚

Question

在过去7天内，我们的辅助服务器失败了三次，并显示以下消息。这些错误意味着什么？为什么要回滚？我附上了oplog窗口的屏幕截图和复制滞后。

凌晨4点左右，服务器出现故障。在3:50左右，复制延迟达到300秒，但这只是5分钟，节点有更多的oplog窗口。

我们使用来自其中一个二级的MMS进行备份，这可能是问题的原因吗？

Mon May 19 03:50:27.146 [rsBackgroundSync] replSet syncing to: xxxx.prod.xxxx.net:17017
Mon May 19 03:50:27.231 [rsBackgroundSync] replSet our last op time fetched: May
19 03:50:16:152
Mon May 19 03:50:27.231 [rsBackgroundSync] replset source's GTE: May 19 03:50:16
:153
Mon May 19 03:50:27.231 [rsBackgroundSync] replSet rollback 0
Mon May 19 03:50:27.231 [rsBackgroundSync] replSet ROLLBACK
Mon May 19 03:50:27.231 [rsBackgroundSync] replSet rollback 1
Mon May 19 03:50:27.231 [rsBackgroundSync] replSet rollback 2 FindCommonPoint
Mon May 19 03:50:27.232 [rsBackgroundSync] replSet info rollback our last optime
:   May 19 03:50:16:152
Mon May 19 03:50:27.232 [rsBackgroundSync] replSet info rollback their last opti
me: May 19 03:50:16:155
Mon May 19 03:50:27.232 [rsBackgroundSync] replSet info rollback diff in end of
log times: 0 seconds
Mon May 19 03:50:27.691 [rsBackgroundSync] replSet rollback found matching event
s at Mar 13 06:12:22:11
Mon May 19 03:50:27.691 [rsBackgroundSync] replSet rollback findcommonpoint scan
ned : 222891
Mon May 19 03:50:27.691 [rsBackgroundSync] replSet replSet rollback 3 fixup
Mon May 19 03:50:30.065 [rsBackgroundSync] replSet rollback 3.5
Mon May 19 03:50:30.065 [rsBackgroundSync] replSet rollback 4 n:7018
Mon May 19 03:50:30.065 [rsBackgroundSync] replSet minvalid=May 19 03:50:16 5379
e1e8:155
Mon May 19 03:50:30.065 [rsBackgroundSync] replSet rollback 4.6
Mon May 19 03:50:30.065 [rsBackgroundSync] replSet rollback 4.7
Mon May 19 03:50:30.443 [rsBackgroundSync] ERROR: rollback cannot find object by
id
Mon May 19 03:50:30.444 [rsBackgroundSync] ERROR: rollback cannot find object by
id
Mon May 19 03:50:30.444 [rsBackgroundSync] replSet rollback 5 d:4 u:7016
Mon May 19 03:50:30.460 [rsBackgroundSync] replSet rollback 6

Answer 1

我们发现主要的oplog以某种方式被破坏了。我们通过在查询后运行hte来找到它

db.oplog.rs.find().sort({$natural:1}).explain()
db.oplog.rs.find().sort({$natural:-1}).explain()

所以我们做了一个主要的步骤，并进行了新的同步。