Shulou(Shulou.com)05/31 Report--

This article introduces the relevant knowledge of "how to solve the problem of slow mongorestore data recovery in Mongo". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

There is a situation where restore data is very slow, and this is what is happening here.

I have also encountered situations where the recovery data is slow or stuck. At that time, I recovered the data in the replication set environment. After checking the log, I found that: if the Secondary node is broken, when the above recovery command is executed on the Primary node, the following error will occur due to the heartbeat mechanism of Arbiter:

2016-03-28T16:56:52.304+0800 I REPL [ReplicationExecutor] Error in heartbeat request to 192.168.37 ReplicationExecutor 27017; Location18915 Failed attempt to connect to 192.168.8.37

And then the whole progress bar got stuck.

Solution:

> rs.remove ()

First remove the delayed or problematic secondery nodes, and then add

This is the end of the content of "how to solve the problem of slow mongorestore data recovery in Mongo". Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.