[CSHARP-3862] .NET 6.0 RC1: Resume of change stream was not possible, as the resume point may no longer be in the oplog.. Created: 16/Sep/21 Updated: 20/Sep/21 Resolved: 20/Sep/21 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | Read Operations |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Brian Buvinghausen | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Driver version 2.13.1 works just fine on .NET 5.0 but as soon as I ported everything over to .NET 6.0 RC1 which dropped on Tuesday and the change streams can no longer resume from the change stream from the tokens. I reverted back to .NET 5.0 just to verify that the tokens were in fact still in the oplog and it starts back up without any issues so clearly something changed in .NET internals as to how change streams are picked back up. Problem occurs in both Windows and Linux so it isn't OS specific. Here is the full stacktrace MongoDB.Driver.MongoCommandException: Command aggregate failed: Resume of change stream was not possible, as the resume point may no longer be in the oplog..
Let me know if you need any additional information/code. |
| Comments |
| Comment by Jeffrey Yemin [ 20/Sep/21 ] |
|
Thanks for updating us. I'm going to close this out but please comment back if you have further issues. |
| Comment by Brian Buvinghausen [ 16/Sep/21 ] |
|
Follow on comment. When I archived the resume tokens generated from .NET 5 I was able to start the process up. The resume tokens generated by .NET 6.0 RC1 are capable of being resumed going forwards so I will just be careful shutting down the queue workers and then archiving the tokens and spinning the services back online so ultimately I am not blocked which is the key thing. |