Driver tries to kill a cursor twice when limit is reached on the first batch

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Minor - P4
    • 3.0.3
    • Affects Version/s: 3.0.2
    • Component/s: Query Operations
    • None
    • Environment:
      linux Ubuntu 14.04.2 LTS
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We have updated our java mongo driver from 2.13.0 to 3.0.2, and since then, we have tons of "killcursors: found 0 of 1" in logs on our secondary servers

      Before the change, we had around 500 logs per hours of it :

      $ sudo grep 2015-06-09T14 /var/log/mongodb/mongodb.log | grep -c killcursors
      511

      since the change, we have around 150 times more of this log :

      sudo grep 2015-06-09T18 /var/log/mongodb/mongodb.log | grep -c killcursors
      78043

      After the rollback, these logs disapeared

        1. 2.13.0.log
          1 kB
        2. 3.0.2.log
          2 kB
        3. killCursor.txt
          0.2 kB

              Assignee:
              Jeffrey Yemin
              Reporter:
              Jean-Philippe Caruana
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: