[DOCS-2221] Note multi-version migration issue in release notes Created: 12/Nov/13  Updated: 11/Jan/17  Resolved: 05/Dec/13

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Major - P3
Reporter: Greg Studer Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 10 years, 10 weeks, 6 days ago

 Description   

Release notes for 2.6:

In 2.4, we allowed a shard to refresh metadata even when the shard name was unknown to the shard - this is dangerous, and is disallowed in 2.6. However, changing this means that migrations TO 2.6 shards FROM 2.4 shards may not have enough information (i.e. the shard name) to begin - and so may error out with:

warning: cannot start recv'ing chunk [

{ _id: MinKey }

,

{ _id: MaxKey }

) :: caused by :: cannot refresh metadata for test.collection before shard name has been set

This should not cause orphaned data or any other problems, but it may interfere with migrations in a multi-version cluster (which we do not support anyway, and is very unlikely if the 2.6 shard has any data on it at all).



 Comments   
Comment by Githook User [ 05/Dec/13 ]

Author:

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

Message: DOCS-2221 relnotes refresh metadata restrictions
Branch: master
https://github.com/mongodb/docs/commit/e17d0f9f28190df0808a6a50f45f5990704ea802

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