Currently the truncate markers are only be created every time we call sampleAndUpdate. Therefore, most of the time, the OplogCapMaintainerThread has a stale version of oplog truncate markers. This means the server status metrics arent very accurate, and we are getting some jumps. e.g. going from 0 -> 2 -> 30 markers (as opposed to seeing it increment every time we create a marker)