The oldest_timestamp invariant check was recently added to ensure that the oldest_timestamp always moves forward. In the old code, if it did not move forward, the out-of-order oldest_timestamp value was ignored. This could potentially cause the process to crash if mongod attempted to perform writes at a timestamp less than the latest oldest_timestamp, but I have yet to see any such crashes.