[SERVER-68318] Add tenant-aware locking for replset setClusterParameter Created: 26/Jul/22 Updated: 17/Aug/22 Resolved: 17/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Gabriel Marks | Assignee: | Gabriel Marks |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Security 2022-08-22 | ||||||||
| Participants: | |||||||||
| Description |
|
Different tenants should be allowed to execute setClusterParameter simultaneously, but not the same tenant. |
| Comments |
| Comment by Gabriel Marks [ 17/Aug/22 ] |
|
This is no longer required after removing on-update-callback from scope. |