[SERVER-51065] compound_hashed_shard_key_zoning.js should upsert into the config database instead of insert Created: 18/Sep/20  Updated: 29/Oct/23  Resolved: 24/Sep/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.8.0

Type: Task Priority: Major - P3
Reporter: Eric Maynard Assignee: Eric Maynard
Resolution: Fixed Votes: 0
Labels: sharding-csrs-stepdown-upkeep, sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-10-05
Participants:
Linked BF Score: 17

 Description   

Writes to config by user request retry even without retryable writes enabled.  This test should use upsert instead of insert to avoid duplicate key errors caused step-down induced race conditions.



 Comments   
Comment by Githook User [ 24/Sep/20 ]

Author:

{'name': 'Eric Maynard', 'email': 'eric.maynard@mongodb.com', 'username': 'ermay12'}

Message: SERVER-51065 compound_hashed_shard_key_zoning.js should upsert into the config database instead of insert
Branch: master
https://github.com/mongodb/mongo/commit/b94a94e51833bb68f993d3e6c85d5e726107e98c

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