[SERVER-57316] Changing a few functions that rely on the presence of epochs/timestamps on config.chunks Created: 01/Jun/21  Updated: 29/Oct/23  Resolved: 16/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:
Backports
Depends
is depended on by SERVER-57060 Rename of a sharded collection must b... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Sharding EMEA 2021-06-14, Sharding EMEA 2021-06-28
Participants:

 Description   

This is the second step towards getting rid of epochs/timestamps on config.chunks.

There are some functions that rely on the presence of epochs/timestamps on config.chunks to indentify a collection. This is fine for 4.4 but not for 5.0 since we plan to remove them. In 5.0 we should use the UUID instead (present on config.collections and config.chunks (since 5.0)).

Below you can find a list of functions that should be addressed:

  1. ShardingCatalogManager::ensureChunkVersionIsGreaterThan
  2. ShardingCatalogManager::clearJumboFlag
  3. ShardingCatalogManager::commitChunkSplit
  4. ShardingCatalogManager::commitChunkMerge
  5. ShardingCatalogManager::commitChunkMigration
  6. Catalog cache refreshes compare the epoch of config.collections and config.chunks to identify inconsistencies.


 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 [ 16/Jun/21 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-57316 Changing a few functions that rely on the presence of epochs/timestamps on config.chunks

(cherry picked from commit 6729afa6c6f081333973601172fafa7c71741508)
Branch: v5.0
https://github.com/mongodb/mongo/commit/93b146a03ef685c1ea777d7470ab12de30fedeb4

Comment by Githook User [ 16/Jun/21 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-57316 Changing a few functions that rely on the presence of epochs/timestamps on config.chunks
Branch: master
https://github.com/mongodb/mongo/commit/6729afa6c6f081333973601172fafa7c71741508

Comment by Githook User [ 15/Jun/21 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-57316 Changing a few functions that rely on the presence of epochs/timestamps on config.chunks

The following functions do not rely on the presence of epochs on config.chunks if there is a timestamp on config.collections:

  • ensureChunkVersionIsGreaterThan cmd.
  • clearJumboFlag cmd.
  • commitChunkMerge/commitChunksMerge.
  • commitChunkSplit.
  • commitChunkMigration.
  • getMaxChunkVersionFromQueryResponse.

(cherry picked from commit 108840e0fdd428435b3fbbc1919ddb05311321c7)
Branch: v5.0
https://github.com/mongodb/mongo/commit/5268977d520f944bdf55e1bd4299ff7429bbe8ff

Comment by Githook User [ 14/Jun/21 ]

Author:

{'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}

Message: SERVER-57316 Changing a few functions that rely on the presence of epochs/timestamps on config.chunks

The following functions do not rely on the presence of epochs on config.chunks if there is a timestamp on config.collections:

Generated at Thu Feb 08 05:41:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.