CursorStream.pipe(stream) halts with event 'drain' #807
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
I have a cursor stream piped to another stream of type BiStream.
This prints the document ids up until batchSize (10K in my case), and then begins to sputter to a halting stop. I found that if I go into BiStream and stop emitting
drainevents, everything proceeds normally through the entire collection.From Node.js Stream docs:
Doesn't seem like drain should affect much, but it halts a CursorStream.