I discovered a bug today that log cursors don't work when log compression is being used. This does not affect printlog nor recovery as those walk the log with *wt_log_scan and they do not use cursors although it does affect the *wt_log_needs_recovery function. ddanderson has written a unit test to combine log cursors and compression testing.
- is depended on by
-
SERVER-18199 WiredTiger changes for MongoDB 3.1.2
- Closed
- is related to
-
WT-1840 log cursors fail with large number of keys
- Closed