[SERVER-78832] AutoGetCollectionForReadLockFree constructor should check the shard version when setting shard key Created: 10/Jul/23  Updated: 29/Oct/23  Resolved: 21/Jul/23

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

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

Issue Links:
Depends
Related
related to SERVER-76197 Lock-free reads on a shard secondary ... Closed
Assigned Teams:
Query Execution
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2023-07-24
Participants:
Linked BF Score: 105

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

Author:

{'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}

Message: SERVER-78832 Make AutoGetCollectionForReadLockFree check the shard version before setting the shard key
Branch: master
https://github.com/mongodb/mongo/commit/516ecab021d7af72ca5d4952290e643bd5018fc8

Comment by Mihai Andrei [ 12/Jul/23 ]

Sending to jordi.serra-torrens@mongodb.com

Comment by Jordi Serra Torrens [ 12/Jul/23 ]

This bug is a more general manifestation of SERVER-76197. In this case, its effects also manifest on primary nodes in the presence of concurrent refineCollectionShardKey operations.

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