It will only run if it can find at least one oplog that is ready for
compaction. Once "getOplogsToBeCompacted()" returns null then a new
compaction task will not be scheduled until a new oplog becomes compactable
(see
Was looking into OplogCompactor due to excessive info level log messages and
noticed that (1) compaction continuously runs using the disk store task thread
pool (is re-scheduled with no delay); and (2) info level messages are in the
nominal (no errors) code path.
It would seem that info level
