The SnapshotThread poses somewhat of a pathological use case for WiredTiger as it repeatedly seeks to the highest key in the oplog in the presence of concurrent inserts to the end of the tree. This operation is inherently unscalable as the seeking to the end of the RecordStore is not wait-free in the presence of concurrent inserts.

We should run our full test suite with the SnapshotThread enabled to find any additional longevity/stability issues.