[SERVER-47986] Introduce a thread to complete the shard version recovery after step-up Created: 06/May/20 Updated: 03/Jun/20 Resolved: 03/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Tommaso Tocci |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | PM-1645-Milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Sprint: | Sharding 2020-06-01, Sharding 2020-06-15 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
At step-up, invalidate all CollectionsShardingState of the collections that have pending outgoing migrations, then schedule a thread to "touch" the namespace so it completes the recovery in case no CRUD operation accesses it. |
| Comments |
| Comment by Tommaso Tocci [ 03/Jun/20 ] |
|
This has been done as part of |