[SERVER-77072] [test-only bug] retry updateMany when directly writing to the CSRS in `merge_all_chunks_on_shard.js` Created: 12/May/23  Updated: 29/Oct/23  Resolved: 07/Jul/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 7.0.0-rc7

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.0
Sprint: Sharding EMEA 2023-06-26, Sharding EMEA 2023-07-10
Participants:
Linked BF Score: 5
Story Points: 1

 Description   

SERVER-75637 tried to fix with retryable writes the WriteConcernError raised by stepdown while trying to set the onCurrentShardSince field on chunk entries. It turns out that this solution is not effective because we're not performing a simple update but an updateMany that by design is not retryable.



 Comments   
Comment by Githook User [ 07/Jul/23 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-77072 Change updateMany to updateOne in order to fully test the desired behavior in jstest

(cherry picked from commit 0de15b79675de9123c61fb46ef8d13e7bd2a7036)
Branch: v7.0
https://github.com/mongodb/mongo/commit/2bf0442cf8bc02d791a0e754e81f29f212802e9e

Comment by Githook User [ 06/Jul/23 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-77072 Change updateMany to updateOne in order to fully test the desired behavior in jstest
Branch: master
https://github.com/mongodb/mongo/commit/0de15b79675de9123c61fb46ef8d13e7bd2a7036

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