[SERVER-58220] Sharded $lookup attempts to run shard pipeline on config server instead of shard-local config database Created: 02/Jul/21  Updated: 29/Oct/23  Resolved: 07/Jul/21

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

Type: Bug Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Hana Pearlman
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-58300 Generalize the concept of a shard-loc... Backlog
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 165

 Description   

With featureFlagShardedLookup enabled, the $lookups when reading from the config.localReshardingOplogBuffer.xx namespace end up targeting the config server rather than reading locally from the shard. This leads resharding's oplog application to miss finding the relevant oplog entry containing the pre/postImage document and causes findAndModify retryable writes to error after the resharding operation completes.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 07/Jul/21 ]

Author:

{'name': 'Hana Pearlman', 'email': 'hana.pearlman@mongodb.com', 'username': 'HanaPearlman'}

Message: SERVER-58220: Do a local read when the collection stores local resharding oplog buffer
Branch: master
https://github.com/mongodb/mongo/commit/0ef0c929cd583f5039a1d13d3b212a18eda27c2c

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