[SERVER-51390] Always refresh database cache on StaleDatabaseVersion Created: 06/Oct/20 Updated: 29/Oct/23 Resolved: 09/Oct/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 4.7.0 |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Tommaso Tocci |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1645-Milestone-2, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Steps To Reproduce: | The following js test reproduces the bug. |
||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
If a mongos receives a StaleDatabaseVersion error, it refreshes its cache only if the shard attached a wantedVersion to the error. This prevent a stale mongos from discovering that a database have been dropped. In fact in this case the shards won't send any wanted version since the database doesn't exist anymore. None of our current tests cover this scenario, so we should also add a test for this. |
| Comments |
| Comment by Githook User [ 09/Oct/20 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |
| Comment by Githook User [ 09/Oct/20 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: Revert " This reverts commit d81fb9e5c454f89b6c41099c8b8ce09c463344c6. |
| Comment by Tommaso Tocci [ 08/Oct/20 ] |
|
ben.caimano I think you are right I'm going to revert this. |
| Comment by Githook User [ 08/Oct/20 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |