[SERVER-57175] Remove reduntant collection refresh on create collection coordinator Created: 25/May/21 Updated: 29/Oct/23 Resolved: 25/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 5.0.0, Backlog |
| Fix Version/s: | 5.0.0-rc1, 5.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Tommaso Tocci |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1965-Milestone-1 | ||
| 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 |
|
In the create collection coordinator we perform a preliminary check to see if the collection has been already shareded. In fact the collection could have been already sharded previously by either another shard collection execution. After acquiring the collection critical section we perform again the very same check, this shouldn't be necessary because no-one else except for the running coordinator could possibly shard the collection. The goal of this ticket is to remove completely the second check that is redundant. |
| 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 [ 26/May/21 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: (cherry picked from commit 172cadf4113b6edaccc40db8cf7d217700f3baf5) |
| Comment by Githook User [ 25/May/21 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |