[SERVER-55819] Chunks timestamp are not updated on resharding transition to persisted state Created: 06/Apr/21 Updated: 29/Oct/23 Resolved: 07/Apr/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jordi Serra Torrens | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-Catalog-Work | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Participants: |
| Description |
|
When the temporary resharding collection is 'renamed' to the original nss, the chunks lastmodEpoch is updated to the new one. However, when featureFlagShardingFullDDLSupportTimestampedVersion is enabled, the chunks 'timestamp' should also be updated to reflect that of the new resharded collection. |
| Comments |
| Comment by Githook User [ 07/Apr/21 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |