[SERVER-67939] run_dbcheck_background.js should be resilient to CappedPositionLost Created: 11/Jul/22  Updated: 29/Oct/23  Resolved: 12/Jul/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.12, 6.0.2, 6.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Yujin Kang Park Assignee: Yujin Kang Park
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.0, v5.0
Sprint: Execution Team 2022-07-25
Participants:
Linked BF Score: 19

 Description   

run_dbcheck_background.js scanning the healthlog may fail due to the collection being truncated, as it is a capped collection. We should check for CappedPositionLost error and retry.



 Comments   
Comment by Uladzimir Makouski [ 10/Aug/22 ]

Requesting v5.0 backport, because this issue has been noticed on v5.0 branch as well: BFG-1355962

Comment by Yujin Kang Park [ 01/Aug/22 ]

The issue this ticket addresses also affects v6.0

Comment by Githook User [ 11/Jul/22 ]

Author:

{'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}

Message: SERVER-67939: run_dbcheck_background.js retry on CappedPositionLost
Branch: master
https://github.com/mongodb/mongo/commit/37f750c8372b7186ae96615a968307936d18e5b2

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