Shulou(Shulou.com)06/01 Report--

replSet error RS102 too stale to catch up

Secondary replica members need to shut down to increase memory. Shut down early. When the server gets up the next day, check rs.status() information and catch "stateStr" : "RECOVERING". In fact, the maintenance window has already been exceeded. Error RS102 too stale to catch up. This error is caught every ten minutes. From mongodb's log file you can see:

Thu Mar 26 20:50:48.561 [rsBackgroundSync] replSet error RS102 too stale to catch up, at least from dal05mgo13.sl.dx:27017Thu Mar 26 20:50:48.561 [rsBackgroundSync] replSet error RS102 too stale to catch upThu Mar 26 21:00:49.632 [rsBackgroundSync] replSet error RS102 too stale to catch up, at least from dal05mgo13.sl.dx:27017Thu Mar 26 21:00:49.632 [rsBackgroundSync] replSet error RS102 too stale to catch upThu Mar 26 21:10:50.701 [rsBackgroundSync] replSet error RS102 too stale to catch up, at least from dal05mgo12.sl.dx:27017Thu Mar 26 21:10:50.701 [rsBackgroundSync] replSet error RS102 too stale to catch upThu Mar 26 21:20:51.770 [rsBackgroundSync] replSet error RS102 too stale to catch up, at least from dal05mgo13.sl.dx:27017Thu Mar 26 21:20:51.770 [rsBackgroundSync] replSet error RS102 too stale to catch up

Confirm Maintenance Window Size

View the maintenance window and oplog size of the master copy:

rs_main:PRIMARY> db.printReplicationInfo()configured oplog size: 23552MBlog length start to end: 38133secs (10.59hrs)oplog first event time: Mon Mar 30 2015 12:00:13 GMT-0500 (CDT)oplog last event time: Mon Mar 30 2015 22:35:46 GMT-0500 (CDT)now: Mon Mar 30 2015 22:35:46 GMT-0500 (CDT)

You can see that the maintenance window is 10 hours and the oplog size is 23G.

It is best to keep the size of the secondary replica's maintenance window consistent with the primary replica's members so that the secondary replica can hold oplog synchronized from the primary replica.

How to rebuild oplog?

Start as standalone and execute the delete and create script as follows:

> use local> db.oplog.rs.drop()> db.createCollection("oplog.rs", {"capped" : true, "size" : 23 * 1024 * 1024}) or> db.runCommand( { create: "oplog.rs", capped: true, size: (23 * 1024 * 1024) } )

RS102 is too stale to catch up.

Copy set error RS102 Too stale to keep up. This means that this node has been separated from the replica set for too long and cannot keep up with the entire cluster. This secondary replica member needs to be resynchronized. Reference:

http://docs.mongodb.org/manual/tutorial/resync-replica-set-member/

The official manual recommends completely resynchronizing members by removing data to implement initial sync.

MongoDB provides two ways to implement initialization synchronization:

Empty the data directory and restart mongod. Allow MongoDB to initialize sync data properly to recover data. This method is simpler, but takes more time to replace the data.

Copy the current data directory from another member of the replica set and restart the machine. This process replaces data faster, but requires more manual steps.

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.