Leads to:

1. build up of cursor counts in mongod
2. slow get-more queries
3. high CPU usage in mongod
4. high memory usage in mongos

Observations:

1. The maxAwaitTimeMS set in the watch command not honoured by queries in mongod - Does not return result nor empty within timeout 
2. The cursor.getnext operation creating new connections and cursors behind the scenes
3. If resume token is not matching any data, what is filling up in mongos memory?