Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-61520

Unable to get change stream data when using hasNext()

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.2.12
    • Component/s: None
    • Labels:
    • ALL

      We set the oplog space size to 50GB, and our data size is about 9000W. We keep the resumeToken in memory, we also use hasNext() and next() to get the change stream data. When a large amount of data is updated, it blocks in the hasNext() method and cannot return true or false, so next() could not execute. But when mongo client is restarted, hasNext() will not block with the same resumeToken. Why are we blocking in the hasNext() method?

            Assignee:
            eric.sedor@mongodb.com Eric Sedor
            Reporter:
            che302@qq.com chen liang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: