[SERVER-30246] $changeNotification cursor hangs when sent to mongos Created: 20/Jul/17 Updated: 30/Oct/23 Resolved: 26/Jul/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Charlie Swanson |
| 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 | ||||
| Steps To Reproduce: | Run an aggregate with a $changeNotification stage on a mongos (shards must be replica sets) |
||||
| Sprint: | Repl 2017-07-31 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
In order to work correctly, the merging logic on mongos needs to know that a cursor is tailable. An aggregation with a $changeNotification is tailable, but doesn't communicate that information, so the merging logic mistakenly hangs, repeatedly asking for the next document, since the cursor id is never set to 0. |
| Comments |
| Comment by Githook User [ 26/Jul/17 ] |
|
Author: {'email': 'charlie.swanson@mongodb.com', 'username': 'cswanson310', 'name': 'Charlie Swanson'}Message: |