-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
Fully Compatible
-
ALL
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Example of the error in question:
OperationFailure("oplog no longer contains the complete write history of this transaction, log with opTime { ts: Timestamp(1770869382, 2242), t: 1 } cannot be found, full error: {'ok': 0.0, 'errmsg': 'oplog no longer contains the complete write history of this transaction, log with opTime { ts: Timestamp(1770869382, 2242), t: 1 } cannot be found', 'code': 217, 'codeName': 'IncompleteTransactionHistory', '$clusterTime': {'clusterTime': Timestamp(1770869595, 7027), 'signature': {'hash': b'\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00', 'keyId': 0}}, 'operationTime': Timestamp(1770869595, 7002)}")
Example for a workload that modifies the oplog size:
https://github.com/10gen/dsi/blob/08572c30d2de9b868432c574a14e96d3bfa534d3/evergreen/system_perf/shared_tasks.yml#L931