2016-04-22T02:34:59.656+0800 [rsBackgroundSync] replSet syncing to: 172.28.11.141:27017
|
2016-04-22T02:34:59.657+0800 [rsBackgroundSync] replSet syncing to: 172.28.11.142:27017
|
2016-04-22T02:34:59.659+0800 [rsBackgroundSync] replSet error RS102 too stale to catch up, at least from 172.28.11.142:27017
|
2016-04-22T02:34:59.659+0800 [rsBackgroundSync] replSet our last optime : Apr 21 23:57:42 5718f876:50a
|
2016-04-22T02:34:59.659+0800 [rsBackgroundSync] replSet oldest at 172.28.11.142:27017 : Apr 22 01:31:16 57190e64:5
|
2016-04-22T02:34:59.659+0800 [rsBackgroundSync] replSet See http://dochub.mongodb.org/core/resyncingaverystalereplicasetmember
|
2016-04-22T02:34:59.659+0800 [rsBackgroundSync] replSet error RS102 too stale to catch up
|
2016-04-22T02:34:59.659+0800 [rsBackgroundSync] replSet RECOVERING
|
2016-04-22T02:34:59.947+0800 [initandlisten] connection accepted from 172.28.0.5:51220 #6 (6 connections now open)
|
2016-04-22T02:35:00.656+0800 [rsSync] replSet still syncing, not yet to minValid optime 57190e64:5
|
|
2016-04-22T05:05:13.225+0800 [rsSync] replSet still syncing, not yet to minValid optime 57190f64:29
|
2016-04-22T05:05:14.131+0800 [rsBackgroundSync] replSet syncing to: 172.28.11.141:27017
|
2016-04-22T05:05:14.133+0800 [rsBackgroundSync] replSet syncing to: 172.28.11.142:27017
|
2016-04-22T05:05:14.134+0800 [rsBackgroundSync] replSet error RS102 too stale to catch up, at least from 172.28.11.142:27017
|
2016-04-22T05:05:14.134+0800 [rsBackgroundSync] replSet our last optime : Apr 21 23:57:42 5718f876:50a
|
2016-04-22T05:05:14.134+0800 [rsBackgroundSync] replSet oldest at 172.28.11.142:27017 : Apr 22 01:35:51 57190f77:35
|
2016-04-22T05:05:14.134+0800 [rsBackgroundSync] replSet See http://dochub.mongodb.org/core/resyncingaverystalereplicasetmember
|
2016-04-22T05:05:14.134+0800 [rsBackgroundSync] replSet error RS102 too stale to catch up
|
2016-04-22T05:05:14.225+0800 [rsSync] replSet still syncing, not yet to minValid optime 57190f77:35
|