[SERVER-15848] copydb appears to take out a G_X lock in some circumstances Created: 28/Oct/14 Updated: 06/Dec/22 Resolved: 15/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | 2.8.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Alvin Richards (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | 28qa | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Operating System: | ALL |
| Sprint: | Quint Iteration 3 |
| Participants: |
| Description |
ProblemFrom copydb.cpp https://github.com/mongodb/mongo/blob/master/src/mongo/db/commands/copydb.cpp#L190
SolutionFor this case, perhaps taking out two DB_X locks rather than a G_X lock. |
| Comments |
| Comment by Asya Kamsky [ 15/Aug/18 ] |
|
copyDB has been removed,
|