[SERVER-61520] Unable to get change stream data when using hasNext() Created: 16/Nov/21 Updated: 31/Jan/22 Resolved: 31/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.2.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | chen liang | Assignee: | Eric Sedor |
| Resolution: | Done | Votes: | 0 |
| Labels: | changestreams | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
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? |
| Comments |
| Comment by Eric Sedor [ 10/Dec/21 ] |
|
Hi che302@qq.com, for this issue we'd like to encourage you to start by asking our community for help by posting on the MongoDB Developer Community Forums. If the discussion there leads you to suspect a bug in the MongoDB server, then we'd want to investigate it as a possible bug here in the SERVER project. Thanks, |