[SERVER-30833] Make ShardRegistry remember the operationTime of the config server read from its last reload Created: 25/Aug/17 Updated: 07/Sep/17 Resolved: 07/Sep/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Nathan Myers |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Repl 2017-09-11 |
| Participants: |
| Description |
|
ChangeStreams needs to be able to know how up-to-date the data in the ShardRegistry is in terms of cluster time. When the shard registry does a read against config.shards as part of its internal reload, it should remember the operationTime returned by that read. |