Had a replicaset member fall behind (not sure why yet)... Saw this in the logs:
Wed Jul 16 01:17:52.274 [rsBackgroundSync] replSet syncing to: shard-modb-s04-0001.prv-openclass.com:27017
Wed Jul 16 01:17:52.472 [rsBackgroundSync] replSet error RS102 too stale to catch up, at least from shard-modb-s04-0001.prv-openclass.com:27017
Wed Jul 16 01:17:52.472 [rsBackgroundSync] replSet our last optime : Jul 10 05:38:14 53a125c6:21a
Wed Jul 16 01:17:52.472 [rsBackgroundSync] replSet oldest at shard-modb-s04-0001.prv-openclass.com:27017 : Jul 15 20:51:06 53c5943a:1
Wed Jul 16 01:17:52.472 [rsBackgroundSync] replSet See http://dochub.mongodb.org/core/resyncingaverystalereplicasetmember
Wed Jul 16 01:17:52.472 [rsBackgroundSync] replSet error RS102 too stale to catch up
Wed Jul 16 01:17:52.553 [rsSync] replSet still syncing, not yet to minValid optime 53c5943a:1
No comments:
Post a Comment