[SERVER-31713] Persisted routing table refreshes cause in-memory routing table invalidations on primaries and secondaries, but should only do so on secondaries Created: 25/Oct/17 Updated: 29/Jan/18 Resolved: 08/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | 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: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2017-11-13 | ||||||||
| Participants: | |||||||||
| Description |
|
We have a couple config.cache.collections field signals on which shard nodes take actions to invalidate their in-memory routing table cache. This is only needed on secondaries, now, so this code should only run on secondaries. |
| Comments |
| Comment by Dianna Hohensee (Inactive) [ 08/Nov/17 ] |
|
|