[SERVER-75888] Rename StaleEpoch to StaleUpstreamRouter Created: 10/Apr/23 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | oldshardingemea | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Catalog and Routing
|
||||||||
| Participants: | |||||||||
| Description |
|
What is currently known as StaleEpoch exception represents means to ensure that two router roles that communicate with each other (e.g. here) are both up-to-date with whatever information they have cached for a particular collection. Because of this, it should have a more appropriate name such as StaleUpstreamRouter. The reason for having "upstream" in the name is that if the "downstream" router is staler, there is no reason for exception to be thrown to the upstream one to refresh. |