[SERVER-57313] Pass the collection epoch and timestamp when building a ChunkType from a config.chunks BSON Created: 01/Jun/21 Updated: 29/Oct/23 Resolved: 08/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc2, 5.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Sergi Mateo Bellido |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1965-Milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v5.0
|
||||||||||||
| Sprint: | Sharding EMEA 2021-06-14 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
This is the first step towards getting rid of epochs and timestamps in config.chunks. The task here is extending ChunkType::fromConfigBSON method with the collection epoch and collection timestamp. Ideally we would like to check that the epoch/timestamp in disk and the ones being passed are the same. However I believe that this is not possible in some situations: the config CC loader can see inconsistencies between config.collections and config.chunks right now. |
| 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 [ 14/Jun/21 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message:
(cherry picked from commit 7b30ab1943ecbb48e8bdbc50bf928eab09f619b5) |
| Comment by Githook User [ 03/Jun/21 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message:
|