[DOCS-13880] Source and target database primary shards should match when renaming unsharded collections Created: 18/Sep/20  Updated: 30/Oct/23  Due: 16/Jul/21  Resolved: 13/Jul/21

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Major - P3
Reporter: Pierlauro Sciarelli Assignee: Alison Huh
Resolution: Fixed Votes: 0
Labels: quick-win
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DOCS-14633 Update renameCollection public docume... Closed
Participants:
Days since reply: 2 years, 28 weeks, 5 days ago
Epic Link: DOCSP-11701
Story Points: 1

 Description   

Description

The renameCollection documentation is not mentioning a current limitation in sharded clusters: it is not supported the rename of an unsharded collection if source and target database primary shards are different.

There is also a test showing that this scenario is expected to fail.

The following sentence should be reformulated.

FROM:
"You cannot rename a sharded collection. You can however rename an unsharded collection in a sharded cluster."

TO something like:

"You cannot rename a sharded collection. You can however rename an unsharded collection in a sharded cluster as long as source and target databases are residing on the same primary shard."

Scope of changes

Impact to Other Docs

MVP (Work and Date)

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



 Comments   
Comment by Githook User [ 23/Jul/21 ]

Author:

{'name': 'alisonjhuh', 'email': 'alison.huh@mongodb.com'}

Message: DOCS-13880 indicate requirement of matching source and target databases on the same primary shard
Branch: v4.2.15
https://github.com/mongodb/docs/commit/d099274f19371a360c5b4d6dc6f4e12b03aa801a

Comment by Githook User [ 13/Jul/21 ]

Author:

{'name': 'alisonjhuh', 'email': 'alison.huh@mongodb.com'}

Message: DOCS-13880 indicate requirement of matching source and target databases on the same primary shard
Branch: v4.0
https://github.com/mongodb/docs/commit/7edcabb073cc859cf79cb8025085615f7198c636

Comment by Githook User [ 13/Jul/21 ]

Author:

{'name': 'alisonjhuh', 'email': 'alison.huh@mongodb.com'}

Message: DOCS-13880 indicate requirement of matching source and target databases on the same primary shard
Branch: v4.2
https://github.com/mongodb/docs/commit/d099274f19371a360c5b4d6dc6f4e12b03aa801a

Comment by Githook User [ 13/Jul/21 ]

Author:

{'name': 'alisonjhuh', 'email': 'alison.huh@mongodb.com'}

Message: DOCS-13880 indicate requirement of matching source and target databases on the same primary shard
Branch: v4.4
https://github.com/mongodb/docs/commit/b09d46ad22fabf205f81927a030fd9ae792651b3

Comment by Pierlauro Sciarelli [ 12/Jul/21 ]

Hey naomi.pentrel, the original description of this ticket still holds for v4.4.

However, starting from v5.0 - that supports sharded collections rename - the sentence should be rewritten as follows (or in a similar form):

"You can rename an unsharded collection in a sharded cluster as long as source and target databases are residing on the same primary shard. It is not supported rename between databases of sharded collections."

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