[SERVER-35554] revisit log severity of bulk insert errors during initial sync oplog application Created: 12/Jun/18  Updated: 29/Oct/23  Resolved: 13/Jun/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 4.0.0-rc4, 4.1.1
Fix Version/s: 4.1.1

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

Issue Links:
Depends
Related
is related to SERVER-21229 Group replicated inserts/deletes duri... Closed
is related to SERVER-33614 move code for grouping replicated ins... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-06-18
Participants:
Linked BF Score: 0

 Description   

Since SERVER-32335, we started grouping inserts during initial sync oplog application. Depending on to the timing of the collection cloning phase and the starting optime of the oplog application phase, we may get DuplicateKey errors from ApplierHelper::InsertGroup and subsequently degrade into doing single inserts. We should revisit the severity of the error log messages from ApplierHelpers::InsertGroup.



 Comments   
Comment by Githook User [ 13/Jun/18 ]

Author:

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

Message: SERVER-35554 lower severity of bulk insert oplog application DuplicateKey error messages during initial sync
Branch: master
https://github.com/mongodb/mongo/commit/4f55ccddac1c821c6a5fcb51348af0333cb886ba

Comment by Githook User [ 13/Jun/18 ]

Author:

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

Message: SERVER-35554 dedup failed bulk insert msg
Branch: master
https://github.com/mongodb/mongo/commit/f0c7d77ffc6f91a861516df015a2de3894521419

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