[SERVER-57190] Use a fire and forget model when triggering best effort refreshes on create collection path Created: 25/May/21 Updated: 29/Oct/23 Resolved: 27/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 5.0.0-rc0 |
| Fix Version/s: | 5.0.0-rc1, 5.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1965-Cleanup, post-rc0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v5.0
|
||||
| Sprint: | Sharding EMEA 2021-05-31 | ||||
| Participants: | |||||
| Description |
|
Currently after committing a new collection to the config server, we are refreshing all the shards with chunks as a best effort so they can warm up their cache. Right now it is done sequentially and waiting for the response for about 30 seconds, however, given the nature of this call, a better approach would be to fire and forget the requests, like this. This would improve the performance of the collection creation, specially in large clusters with a lot of chunks where the optimized path was taken. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 27/May/21 ] |
|
Author: {'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: (cherry picked from commit 105b03e1250bc3c412566be6262a155d764d8c32) |
| Comment by Githook User [ 27/May/21 ] |
|
Author: {'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: |