When secondary reads must take the PBWM lock to read without a timestamp, all writes become visible. At this point, an operation holding the PBWM lock should not be allowed to start reading with a timestamp in a different snapshot, because writes and catalog operations may appear to vanish.
- is duplicated by
SERVER-44489 When i add index on primary the SECONDARY crashed
- related to
SERVER-41582 Investigate disallowing DBDirectClient from changing the storage engine ReadSource