[SERVER-81444] Don't use temp:true collections for $out on sharded deployments Created: 26/Sep/23 Updated: 06/Nov/23 Resolved: 02/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 135 | ||||||||||||||||
| Description |
|
The 'temp' property of collections is a replica-set level concept – it is not sharding-aware. As we prepare to support $out to collections tracked on the sharding catalog (unsplittable collections in the contest of PM-3229, and sharded collections later on PM-1931), $out can no longer use on 'temp: true' on sharded clusters. Instead, on shard servers, $out will write down the temporary collections it uses to a collection, and these will be garbage-collected on step-up. |
| Comments |
| Comment by Githook User [ 02/Oct/23 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |