[SERVER-35670] Add test that if a shard already has a cache entry for a database without a version, refreshing causes the entry to be updated with the version Created: 19/Jun/18 Updated: 29/Oct/23 Resolved: 20/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2018-07-02 | ||||||||
| Participants: | |||||||||
| Description |
|
This ensures that if a shard had cached a database entry without a version in a 4.0 cluster while in FCV 3.6, then upgrading the cluster to 4.2 binaries will cause the next request that has a database version attached to cause the shard to refresh and pick up the version and write it to its on-disk cache so that the version can also be picked up by secondaries. |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 20/Jun/18 ] |
|
Whoops, forgot to squash the commits into one. |
| Comment by Githook User [ 20/Jun/18 ] |
|
Author: {'username': 'EshaMaharishi', 'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com'}Message: |
| Comment by Githook User [ 20/Jun/18 ] |
|
Author: {'username': 'EshaMaharishi', 'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com'}Message: |