[SERVER-34685] Mongos exits when non-existent resume token is supplied Created: 26/Apr/18 Updated: 27/Apr/18 Resolved: 27/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | avi | Assignee: | Charlie Swanson |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Query 2018-05-07 | ||||||||
| Participants: | |||||||||
| Comments |
| Comment by Charlie Swanson [ 27/Apr/18 ] |
|
Hi aviziv, After some investigation we were able to reproduce the issue with your example BinData. We believe this issue is a duplicate of If you are still able to reproduce the failure when running with version 4.0.0-rc0 (not yet released, stay tuned), please re-open this issue and we will investigate further. |
| Comment by Charlie Swanson [ 26/Apr/18 ] |
|
Can you post the backtrace from the logs for the node that crashed? |
| Comment by avi [ 26/Apr/18 ] |
|
Sorry, probably hit enter too early. So, when a correct "resume after" token is supplied to collection watch through Mongos all is well and we receive change events. When a non-existent resume token (well formatted) is supplied then Mongos crashes. Example of what we observe with a non-existent token: {{> db.ourCollection.watch( [], { resumeAfter : { "_data" : new BinData(0, "aaagf94AAADCRmRfaWQAZFrgY9/zjbt2ewaaiABaEASOM5i0AiZI2YBeXu99TFx2BA==") } } ); The bug occurs in latest version (3.6.4, 3.6, 3) and unstable (3.7.5, 3.7) latest version |