[SERVER-66336] ConfigsvrCoordinators initial checkpoint may incur in DuplicateKey error Created: 10/May/22  Updated: 29/Oct/23  Resolved: 07/Jun/22

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 6.0.0-rc0
Fix Version/s: 6.0.0-rc9, 6.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Jordi Serra Torrens Assignee: Silvia Surroca
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-65930 DDL coordinators and rename participa... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.0
Sprint: Sharding EMEA 2022-05-30, Sharding EMEA 2022-06-13
Participants:

 Description   

ConfigsvrCoordinators (such as SetUserWriteBlockModeCoordinator and SetClusterParameterCoordinator) call insert a coordinator state document to initially checkpoint the operation on disk. Since the write is using a concern with timeout, it could happen the following:

  1. Coordinator starts and tries to insert the document
  2. The document is locally written but not yet majority committed
  3. The write concern timeout is hit
  4. The coordinator retries
  5. The retry fails because the document had already been inserted so a DuplicateKey error is thrown


 Comments   
Comment by Githook User [ 08/Jun/22 ]

Author:

{'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}

Message: SERVER-66336 ConfigsvrCoordinators initial checkpoint may incur in DuplicateKey error
Branch: v6.0
https://github.com/mongodb/mongo/commit/5c874317f98dbb061fdb98f65f2cc44c096677c1

Comment by Githook User [ 07/Jun/22 ]

Author:

{'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}

Message: SERVER-66336 ConfigsvrCoordinators initial checkpoint may incur in DuplicateKey error
Branch: master
https://github.com/mongodb/mongo/commit/2f3753e5c76a4dd71406ec445d045d3d1020bc4b

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