Erick

@jipperinbham Thank you for verifying my suspicions.

@a-magdy I have developed my own nodejs based solution on oplog streams and another git package if you are interested. It provides oplog updates between your old source DB and...

@a-magdy been real busy I have not had time to get back to the above, will try again later this week early next.

I am also trying to use 2.0.2 and seeing similar issues. However, I am using a replica set with TLS encryption and was trying to figure out if that would...

Sorry, should have updated this, I got it to work. It all comes down to making sure you are connected to the 'local' DB so that the oplog collection is...

I have made the following changes to *stream.js* which have made the symptoms better, but not perfect. ``` async function time() { if (ts) return (typeof ts !== 'number') ?...

So I chased this far enough to know that in the mongodb npm driver, collection.js checks for and translates timeout, ie. ``` // Translate to new command option noCursorTimeout if(typeof...

Next steps I hacked mongodb npm module, *lib/collection.js* ``` // Translate to new command option noCursorTimeout if(typeof newOptions.timeout == 'boolean') newOptions.noCursorTimeout = newOptions.timeout; newOptions.noCursorTimeout = false; // Merge in options...

I think I found the real issue, the index.js code is not restarting the tail on timeout. So I am testing the following. ``` function onerror(err) { if (/cursor (killed...

The above appears to work, I will create a PR to contrib this back. Since I am using TLS connections across the wire this may have something to do with...