[SERVER-72872] Add a specific configsvr command to retrieve the historical placement metadata of a namespace/cluster Created: 16/Jan/23 Updated: 29/Oct/23 Resolved: 30/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Paolo Polato | Assignee: | Paolo Polato |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06 |
| Participants: |
| Description |
|
The ShardingCatalogClient offers a set of API methods to retrieve placement metadata on a namespace at a given point in time. Today, these methods are implemented as an local/remote aggregation query that inspects the content of config.placementHistory. Nevertheless, such implementation may return inconsistent results during the execution of a setFCV command from/to version 7.0. The problem could be avoided if the logic accessing the config catalog where under exclusive control of the config server. |
| Comments |
| Comment by Githook User [ 27/Jan/23 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: |