[SERVER-48988] Add a test to check operation threads do not convoy after throwing stale config Created: 19/Jun/20 Updated: 29/Oct/23 Resolved: 30/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1645-Milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2020-06-29 |
| Participants: |
| Description |
|
SERVER-45983 simplified the way the shard version is refreshed in a shard by doing it on a separate thread and executing a migration recovery if needed, making sure we have a reliable shard version after a refresh. To make sure that this new behavior is not causing a convoy of refresh threads if several concurrent operations hits the shard, we want to another test that should check the number of collection metadata refreshes before and after this situation. |
| Comments |
| Comment by Githook User [ 30/Jun/20 ] |
|
Author: {'name': 'Marcos José Grillo Ramírez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: |