Info

Unclean shutdown on an Atlas node hosting a time-series collection appears to have left two v1 bucket documents in a structurally corrupted state, such that time-series validation reports: The indexes in time-series bucket data fields are not consecutively increasing from '0'. This corresponds to the kTimeIndexNotIncreasing timeseries validation result in validate_adaptor.cpp and indicates that the data. numeric keys in the bucket are no longer the expected 0..N-1 sequence. Since this happened when validating after an unclean shutdown, it seems possible that time series writes that were in-flight during a crash left the system in an inconsistent state, even after WT replayed the journal and rolled back to the last good checkpoint. There are more details in the linked AF ticket.

Top User Comments

Steps to Reproduce