[SERVER-54283] Move the legacy dropDatabase/Collection path to execute from the shard Created: 04/Feb/21 Updated: 29/Oct/23 Resolved: 09/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0-alpha4 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| 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 | ||||||||||||
| Sprint: | Sharding 2021-02-22 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 31 | ||||||||||||
| Description |
|
Currently, the shard forwards the legacy dropDatabase/Collection paths to execute on the config server. This however causes DistLock conflicts with locks which are now taken by the shard. |
| Comments |
| Comment by Githook User [ 09/Feb/21 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: ... rather than forwarding to the config server |
| Comment by Githook User [ 06/Feb/21 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |
| Comment by Githook User [ 05/Feb/21 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: Revert " This reverts commit 12585ccedf9215901d21351d6f5da9f2dd337395. |
| Comment by Githook User [ 05/Feb/21 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |
| Comment by Tommaso Tocci [ 05/Feb/21 ] |
|
kaloian.manassiev I think that you can also re-enable the basic_drop_coll.js test in the sharding_continuous_config_stepdown.yml suite in the context of this ticket. |