[SERVER-52972] Handle SnapshotUnavailable and LockTimeout errors when running transaction to drop a role Created: 20/Nov/20 Updated: 29/Oct/23 Resolved: 11/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Sara Golemon |
| 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: | Security 2020-12-14, Security 2020-12-28, Security 2021-01-11, Security 2021-01-25, Security 2021-02-08, Security 2021-02-22 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 33 | ||||||||
| Description |
|
These errors are pretty likely to occur as other operations in the system are running. For example, an index build on the admin.system.users collection right after the read timestamp for the transaction was established could cause the snapshot to become unavailable. |
| Comments |
| Comment by Githook User [ 11/Feb/21 ] |
|
Author: {'name': 'Sara Golemon', 'email': 'sara.golemon@mongodb.com', 'username': 'sgolemon'}Message: |