The timestamp that oplog reads use for proper visibility is a global value that is set asynchronously. Currently, it is possible for rollback to do reads on the oplog as part of its work, and such reads may be subject to stale oplog visibility. SERVER-34091 is one example of this. To ensure no other problems are lurking, we should set the oplog visibility timestamp synchronously when rollback starts.