[SERVER-28371] after migration completes, shard donor primary sends oplog message to secondaries to invalidate chunk metadata Created: 17/Mar/17  Updated: 25/May/17  Resolved: 25/May/17

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

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

Issue Links:
Duplicate
duplicates SERVER-27713 Create OpObservers for config.collect... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

secondaries should be able to just refresh as soon as they receive the message because the oplog message will be written after chunk metadata is refresh on the primary – after the chunk metadata updates have been persisted.

This should probably be done at the end of the migration critical section

It's only necessary to do this on the donor shard, whose secondaries could return stale data because the chunk has been moved elsewhere. Recipient shards only become aware of their data when they get requests for it via a higher shard version.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 17/Apr/17 ]

Must decided whether to do this ticket or SERVER-27713, not both.

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