[SERVER-40994] renameCollection should always lock system.views collection after everything else Created: 03/May/19 Updated: 29/Oct/23 Resolved: 14/May/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.12 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Xiangyu Yao (Inactive) | Assignee: | Xiangyu Yao (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Storage NYC 2019-05-06, Storage NYC 2019-05-20 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 5 | ||||||||||||
| Description |
|
renameCollection now locks source and target namespaces sequentially based on their resourceIds order. But we should make an exception for "db.system.views" collection because any operation that triggers a view catalog reload will lock "db.system.views" in IS mode in the end. Therefore, renameCollection should always lock system.views in the end. |
| Comments |
| Comment by Githook User [ 14/May/19 ] |
|
Author: {'name': 'Xiangyu Yao', 'username': 'xy24', 'email': 'xiangyu.yao@mongodb.com'}Message: |