[SERVER-7221] renameCollection should only take global lock when crossing lock/db boundaries Created: 01/Oct/12 Updated: 06/Dec/22 Resolved: 19/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Participants: |
| Description |
|
See summary |
| Comments |
| Comment by Asya Kamsky [ 19/Oct/18 ] |
|
It looks like currently it's already the case that renameCollection does not take global W lock when rename happens within the same DB. |