[SERVER-76626] Investigate test failures for concurrent $out and shardCollection commands Created: 27/Apr/23  Updated: 29/Oct/23  Resolved: 09/May/23

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

Type: Bug Priority: Major - P3
Reporter: Gil Alon Assignee: Gil Alon
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-76848 [false alarm] $out does not ensure th... Closed
is related to SERVER-74061 Support $out for time-series on secon... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.0
Sprint: QI 2023-05-15
Participants:

 Description   

During SERVER-74061 we noticed occasional failures in concurrency tests timeseries_agg_out.js that failed with the following error.

Found metadata inconsistencies: Found collection on non primary shard with mismatching UUID 

These errors happened were noticed with time-series collections. The errors stopped when we changed shardCollection to a no-op, but this error should be investigated further and the shardCollection should be changed from a no-op.



 Comments   
Comment by Githook User [ 08/May/23 ]

Author:

{'name': 'Gil Alon', 'email': 'gil.alon@mongodb.com', 'username': 'galon1'}

Message: SERVER-76626 Add a lock to the view namespace when renaming buckets collection for $out
Branch: master
https://github.com/mongodb/mongo/commit/b8a5d658f5e9df7a4eab1c9310d9a708cbc99a05

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