Uploaded image for project: 'Java Driver'
  1. Java Driver
  2. JAVA-3756

When continued polling via the java driver using a resume token not in oplog, leads to mongos's crashing

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Done
    • Affects Version/s: 3.6.4
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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?

        Attachments

          Activity

            People

            Assignee:
            rachelle.palmer Rachelle Palmer
            Reporter:
            anmenon@adobe.com Anand Menon
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: