In secondary_reads_timestamp_visibility.js, we wait for the secondary's readConcernMajorityOpTime to advance, then read from the secondary. However, when majority read concern is disabled, the readConcernMajorityOpTime is set based on the node's knowledge of the majority commit point and does not imply that the node has applied through that point. This causes us to read from the secondary before it has applied the operations. We must also wait for the secondary to apply the operations.