[SERVER-48335] Indexes rebuilt via rollback-via-refetch should not retry skipped records Created: 20/May/20  Updated: 29/Oct/23  Resolved: 26/May/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.4.0-rc8, 4.7.0

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

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Execution Team 2020-06-01
Participants:
Linked BF Score: 50

 Description   

Rollback-via-refetch will call retrySkippedRecords which is only intended to be called on primaries. It can fail when not called on a primary.



 Comments   
Comment by Githook User [ 27/May/20 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-48335 Indexes rebuilt via rollback-via-refetch should not retry skipped records

(cherry picked from commit 8f829788f45667acbf8d24c03a19365351d269bc)
Branch: v4.4
https://github.com/mongodb/mongo/commit/dde5cb0c7ae1c70e7c7398f7b821598294d03138

Comment by Githook User [ 21/May/20 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-48335 Indexes rebuilt via rollback-via-refetch should not retry skipped records
Branch: master
https://github.com/mongodb/mongo/commit/8f829788f45667acbf8d24c03a19365351d269bc

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