[SERVER-30226] Force the recipient shard to refresh its metadata after migration commit Created: 19/Jul/17  Updated: 30/Oct/23  Resolved: 28/Nov/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.6.1, 3.7.1

Type: Task Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Completed:
Backport Requested:
v3.6
Sprint: Sharding 2017-12-04
Participants:

 Description   

In the current sharding migration protocol, the recipient shard finds about the migration commit lazily, when it gets hit with a query with a newer shard version.

With the secondaries chunk aware project, where shards sync metadata from the config server and persist it locally, this laziness opens up a longer period where a crash of a shard's primary can render it unable to fetch the latest routing information from the config server.

Because of this we should implement a best-effort attempt to force the recipient shard's primary to refresh the latest routing information after the migration commits.



 Comments   
Comment by Githook User [ 06/Dec/17 ]

Author:

{'name': 'Dianna Hohensee', 'username': 'DiannaHohensee', 'email': 'dianna.hohensee@10gen.com'}

Message: SERVER-30226 Best effort make the recipient shard refresh its metadata after migration commit

(cherry picked from commit a8ec0b2576f03db6792c6b953f86daba4a99a582)
Branch: v3.6
https://github.com/mongodb/mongo/commit/cbbafbafd414ab544231932cf7e0383ec07b2426

Comment by Dianna Hohensee (Inactive) [ 28/Nov/17 ]

Had to recommit because I forgot to ignore a StatusWith via Status::ignore()

Comment by Githook User [ 28/Nov/17 ]

Author:

{'name': 'Dianna Hohensee', 'username': 'DiannaHohensee', 'email': 'dianna.hohensee@10gen.com'}

Message: SERVER-30226 Best effort make the recipient shard refresh its metadata after migration commit
Branch: master
https://github.com/mongodb/mongo/commit/a8ec0b2576f03db6792c6b953f86daba4a99a582

Comment by Githook User [ 28/Nov/17 ]

Author:

{'name': 'Dianna Hohensee', 'username': 'DiannaHohensee', 'email': 'dianna.hohensee@10gen.com'}

Message: Revert "SERVER-30226 Best effort make the recipient shard refresh its metadata after migration commit"

This reverts commit 2d2a0ebee73a4a1652ae1f1373b2aa47856ddb55.
Branch: master
https://github.com/mongodb/mongo/commit/1de52d81af03d5d1ed8b878eaf73747ceb333140

Comment by Githook User [ 28/Nov/17 ]

Author:

{'name': 'Dianna Hohensee', 'username': 'DiannaHohensee', 'email': 'dianna.hohensee@10gen.com'}

Message: SERVER-30226 Best effort make the recipient shard refresh its metadata after migration commit
Branch: master
https://github.com/mongodb/mongo/commit/2d2a0ebee73a4a1652ae1f1373b2aa47856ddb55

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