[SERVER-33452] Add support for chunk owner shard history to ChunkType Created: 22/Feb/18 Updated: 29/Oct/23 Resolved: 14/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Martin Neupauer |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2018-03-12, Sharding 2018-03-26 |
| Participants: |
| Description |
|
This ticket covers the work for introducing a history array of the shards, which owned a chunk at particular timestamp. It includes serialization and deserialization and for both the config server and shard format. As part of this task we should consider whether it makes sense to start using IDL for ChunkType instead of piling more parsing/serialization code and unit-tests to it. Writing unit-tests especially would be unnecessary since this is covered by IDL. |
| Comments |
| Comment by Githook User [ 14/Mar/18 ] |
|
Author: {'email': 'martin.neupauer@mongodb.com', 'name': 'Martin Neupauer', 'username': 'MartinNeupauer'}Message: The Chunk type has an array of the past history that we maintain in the sharding manager. |
| Comment by Githook User [ 14/Mar/18 ] |
|
Author: {'email': 'martin.neupauer@mongodb.com', 'name': 'Martin Neupauer', 'username': 'MartinNeupauer'}Message: Revert " This reverts commit 5b42a86b74380953db29455dc68e133166c81005. |
| Comment by Githook User [ 14/Mar/18 ] |
|
Author: {'email': 'martin.neupauer@mongodb.com', 'name': 'Martin Neupauer', 'username': 'MartinNeupauer'}Message: The Chunk type has an array of the past history that we maintain in the sharding manager. |
| Comment by Martin Neupauer [ 27/Feb/18 ] |
|
We will revisit the IDL later as we would have to create 2 IDL definitions - one for a config server and one for a shard server as they persist the routing table differently. |