[SERVER-30437] Stop the shard chunk loader from scheduling persistence tasks with mixed version chunks Created: 31/Jul/17 Updated: 30/Oct/23 Resolved: 11/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.12 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| 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 2017-08-21 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
It's possible for a remote query to the config.chunks to return results containing chunks that change version epoch in the middle, if the query executes around a drop and recreate of a collection. The ShardServerCatalogCacheLoader currently schedules such results for persistence and deals with it down the line. Instead, it should just avoid scheduling such tasks, and thus avoid special handling later. An ConflictingOperationInProgress error must be returned to the caller if mixed results are found, to meet the CatalogCache's expectations. |
| Comments |
| Comment by Githook User [ 11/Aug/17 ] |
|
Author: {'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@10gen.com'}Message: |