[SERVER-20102] Using capped collection insert notifier can delay shutdown or drop Created: 24/Aug/15 Updated: 19/Sep/15 Resolved: 31/Aug/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Querying |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.8 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Participants: |
| Description |
|
If one uses await data with a tailable capped collect it will cause shutdown to wait for the timeout of the notifier. In addition clients will wait too long if a collection is dropped during their wait. In short, we should notify_all if a collection is dropped/destroyed. |
| Comments |
| Comment by Githook User [ 31/Aug/15 ] |
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: |