I have a 3 member replica set (no sharding) running mongodb version 2.4.8.
Using MMS (Mongo Monitoring) I can see that on 7th July 2014 at 12:00 my "replication oplog window" dropped from 2777.78 hours to 68 hours at its lowest point.
Looking back at my log of changes on this date I can see database profiling was enabled that morning.
"db.setProfilingLevel(0)" to disable profiling was executed an hour ago on all collections and on all members of the replica set (PRIMARY FIRST).
An hour later my "replication oplog window" counter is still showing only 102 hours. Will this take time to increase again or should I be looking for another cause ?
Thank you Scott