[SERVER-33795] remove backwards compatible distlock from sharding catalog commands Created: 09/Mar/18 Updated: 29/Oct/23 Resolved: 12/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.7.2 |
| Fix Version/s: | 3.7.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2018-03-26 |
| Participants: |
| Description |
|
The backwards compatible distlock was a distlock taken by sharding catalog commands on a database's name, plus "-movePrimary." It was taken by the sharding catalog commands in v3.6, because prior to v3.6, movePrimary had a bug that it took the database distlock with this "-movePrimary" suffix, rather than just the database's name. Now that we don't need to support backwards compatibility with <v3.6, we can remove the places where we take this backwards compatible distlock. |
| Comments |
| Comment by Githook User [ 12/Mar/18 ] |
|
Author: {'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi', 'username': 'EshaMaharishi'}Message: |