[SERVER-37901] Two subsequent invalidations due to writes on the same session one after the other do not synchronize with each other Created: 02/Nov/18 Updated: 05/Nov/18 Resolved: 05/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Sharding 2018-11-19 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 18 | ||||||||||||
| Description |
|
Because the threads spawned by MongoDSessionCatalog::invalidateSessions get detached, two invalidations of the same session one after the other will not synchronize with each other and the second one can fail with a ConflictingOperationInProgress: Session already killed exception. |