[SERVER-27713] Create OpObservers for config.collections writes to update the in-memory chunk metadata data structures Created: 17/Jan/17  Updated: 06/Dec/17  Resolved: 15/Jun/17

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

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

Issue Links:
Duplicate
is duplicated by SERVER-28371 after migration completes, shard dono... Closed
Gantt Dependency
has to be done before SERVER-28948 open up secondaries to checking shard... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-05-08, Sharding 2017-05-29, Sharding 2017-06-19
Participants:

 Description   
  • If the 'lastConsistentCollectionVersion' field of the shard config.collections collection gets updated, a secondary must invalidate the in-memory chunk cache so that it refreshes.
  • If an entry in the config.collections collection on a shard gets removed, the in-memory chunk cache must be invalidated so that a refresh is attempted, and nothing found.


 Comments   
Comment by Githook User [ 15/Jun/17 ]

Author:

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

Message: SERVER-27713 create an OpObserver for shard chunk metadata updates
Branch: master
https://github.com/mongodb/mongo/commit/9c3099ca1e4a33af44771543626601ab3eab8750

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

Must decide whether to do this ticket or SERVER-28371.

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