-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSHARP-5204: Test Heartbeats don't gossip cluster time #1665
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good overall. Some question regarding the timings + failed test on EG.
tests/MongoDB.Driver.Tests/Specifications/sessions/SessionsProseTests.cs
Outdated
Show resolved
Hide resolved
tests/MongoDB.Driver.Tests/Specifications/sessions/SessionsProseTests.cs
Show resolved
Hide resolved
tests/MongoDB.Driver.Tests/Specifications/sessions/SessionsProseTests.cs
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please check Evergreen failures, as new test is failing for some variants.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
I've scheduled additional EG tasks to test stability of this test. Please double check that.
It turns out we were already not gossiping cluster times in our monitoring connections. Our monitors send hello requests which use a
NoCoreSession
instance when the wire protocol command is created for a hello request. ANoCoreSession
instance has a nullClusterTime
which cannot be changed and callingsession.AdvanceClusterTime
is also a no-op for aNoCoreSession
. So this PR just adds the new prose test described in the Drivers spec update: mongodb/specifications@b76cbf9