[SERVER-33699] multiApply() should return early on any writer thread errors Created: 06/Mar/18  Updated: 29/Oct/23  Resolved: 07/Mar/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.7.3

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-03-12
Participants:

 Description   

Currently in multiApply(), which takes a vector of oplog entries and distributes them across a set of writer threads to apply in parallel, any errors reported by the writer threads are stored in statusVector and returned at the end of the function. It may be possible to exit this function early after all the writer threads have finished running here on any writer errors instead of running the post oplog application steps. This should be fine because we will abort the process during steady state replication, and the initial synced will reset the database state before retrying.



 Comments   
Comment by Githook User [ 07/Mar/18 ]

Author:

{'email': 'benety@mongodb.com', 'name': 'Benety Goh', 'username': 'benety'}

Message: SERVER-33699 multiApply() returns early on any writer thread errors
Branch: master
https://github.com/mongodb/mongo/commit/78c59aa605f5cd9948b2e04a8b84a9e26f8a3f8e

Generated at Thu Feb 08 04:34:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.