[SERVER-54301] Add correctness tests of recovery using history store Created: 04/Feb/21  Updated: 29/Oct/23  Resolved: 07/Jun/21

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 5.0.0-rc2, 5.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Kelsey Schubert Assignee: Vishnu Kaushik
Resolution: Fixed Votes: 0
Labels: post-rc0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on WT-7426 Set write generation number when the ... Closed
depends on SERVER-56590 Oplog truncation should correctly han... Closed
Problem/Incident
Related
is related to WT-7117 RTS to skip modifies that are more re... Closed
is related to WT-7159 Always write on-disk update as a full... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Repl 2021-02-22, Repl 2021-03-08, Repl 2021-03-22, Repl 2021-04-05, Storage - Ra 2021-04-19, Repl 2021-05-03, Repl 2021-05-17, Repl 2021-05-31, Repl 2021-06-14
Participants:
Linked BF Score: 153

 Description   

In WT-7117 and WT-7159, we've identified a gap in our MongoDB test coverage. We should ensure that we have adequate test coverage of MongoDB crash recovery that requires the use of the history store to catch future bugs in this space.

See the workload described in WT-7159 as an example of a workload in MongoDB that utilizes the history store and tests recovery.



 Comments   
Comment by Githook User [ 11/Jun/21 ]

Author:

{'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}

Message: SERVER-54301 Add correctness tests of recovery using history store
Branch: v5.0
https://github.com/mongodb/mongo/commit/4b0c7c070bce44b5c8c8b95fc931d336aa3e25c3

Comment by Githook User [ 07/Jun/21 ]

Author:

{'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}

Message: SERVER-54301 Add correctness tests of recovery using history store
Branch: master
https://github.com/mongodb/mongo/commit/116fc60f5ac5bb5d2faf80624399efcdea79e408

Comment by Githook User [ 05/May/21 ]

Author:

{'name': 'Lingzhi Deng', 'email': 'lingzhi.deng@mongodb.com', 'username': 'ldennis'}

Message: Revert "SERVER-54301 Add correctness tests of recovery using history store"

This reverts commit a5b95e6d0a85bdea4751f5469022f37738bb25d4.
Branch: master
https://github.com/mongodb/mongo/commit/f8ff063b74db74dc473fc5a49eb798976ac81b6a

Comment by Githook User [ 27/Apr/21 ]

Author:

{'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}

Message: SERVER-54301 Add correctness tests of recovery using history store
Branch: master
https://github.com/mongodb/mongo/commit/a5b95e6d0a85bdea4751f5469022f37738bb25d4

Comment by Vamsi Boyapati [ 21/Apr/21 ]

This is blocked by WT-7426, we understand the issue and working on the fix.

Comment by Alexander Gorrod [ 20/Apr/21 ]

I believe the failure is related to index consistency. chenhao.qu is that the case here? lingzhi.deng is it possible that different documents are causing updates to the same index, and those document updates happen in different, overlapping transactions?

Comment by Githook User [ 03/Mar/21 ]

Author:

{'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}

Message: Revert "SERVER-54301 Add correctness tests of recovery using history store"

This reverts commit 297904e17aaa5351d729685b70b97027e44f0cf9.
Branch: master
https://github.com/mongodb/mongo/commit/37dc18b365d3279df10f812e0e388bf08acb8e60

Comment by Githook User [ 02/Mar/21 ]

Author:

{'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}

Message: SERVER-54301 Add correctness tests of recovery using history store
Branch: master
https://github.com/mongodb/mongo/commit/297904e17aaa5351d729685b70b97027e44f0cf9

Generated at Thu Feb 08 05:33:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.