[DOCS-13127] Investigate changes in SERVER-42299: Upgrade/downgrade for config.chunks and config.tags Created: 16/Oct/19  Updated: 13/Nov/23  Resolved: 18/Mar/20

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 4.3.1, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: docs-earlyOpen, docs-investigating
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-42299 Upgrade/downgrade for config.chunks a... Closed
Related
related to DOCS-12951 Investigate changes in SERVER-42368: ... Closed
Participants:
Days since reply: 3 years, 47 weeks ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

This patch disabled chunk migrations, splits, and merges while the setFeatureCompatibilityVersion command is running on the config server primary in a sharded cluster. Running each command during this window will fail with `ConflictingOperationInProgress`.

Description of Linked Ticket

For refine a collection's shard key, the formats of documents in config.chunks and config.tags were changed to allow updating their min boundaries without needing to update their _ids. In particular, _id in config.chunks is no longer a string concatenation of namespace and minbound and _id in config.tags is no longer an object containing namespace and minbound.

As part of this ticket, the server should be changed to:

  • Gate the new format on FCV 4.4 and change the BSONField for the ChunkType class to expect _id as an OID
    • Note SERVER-42106 made _id a string representation of an OID to defer upgrade/downgrade work until this ticket
  • Upgrade (through setFeatureCompatibilityVersion command) should iterate through each document in config.chunks and config.tags and change their _ids to be in the new format
  • Vice versa for downgrade through setFCV

In addition to basic integration testing, add integration coverage to ensure migrations in mixed binary version clusters work and that zone boundaries are respected before and after an upgrade/downgrade.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 18/Mar/20 ]

Author:

{'email': 'kay.kim@10gen.com', 'name': 'Kay Kim', 'username': 'kay-kim'}

Message: DOCS-12951, DOCS-13127: 4.4 shard key value size, fcv upgrade/downgrade for shards
Branch: master
https://github.com/mongodb/docs/commit/580eb74530dac39751841a0699da999426320616

Generated at Thu Feb 08 08:07:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.