-
Notifications
You must be signed in to change notification settings - Fork 246
DRIVERS-2972: add message requirement to ServerDescription.error #1729
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
Changes from 3 commits
ea5698d
6b75475
2668eb9
889e3dd
75ce4dd
bc971f2
5d121b1
21187a9
b7adc0b
b6dfeee
07976f0
cd84c0e
a2bd209
becaa6b
47777df
483db4e
8bf359e
70532c7
9d51f24
cdb27c9
e97908e
4b8516d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -226,7 +226,8 @@ Fields: | |
field in the server's hello or legacy hello response, in the case that the server reports an address different from | ||
the address the client uses. | ||
|
||
- (=) `error`: information about the last error related to this server. Default null. | ||
- (=) `error`: information about the last error related to this server. Default null. MUST contain | ||
or be able to produce a string describing the error. | ||
|
||
- `roundTripTime`: the duration of the hello or legacy hello call. Default null. | ||
|
||
|
@@ -871,7 +872,8 @@ if serverDescription.maxWireVersion >= 17: # MongoDB 6.0+ | |
topologyDescription.maxSetVersion = serverDescription.setVersion | ||
else: | ||
# Stale primary. | ||
# replace serverDescription with a default ServerDescription of type "Unknown" | ||
# replace serverDescription with a default ServerDescription of type "Unknown" and an error | ||
# field describing that that primary was stale | ||
checkIfHasPrimary() | ||
return | ||
else: | ||
|
@@ -889,7 +891,9 @@ else: | |
) | ||
): | ||
# Stale primary. | ||
# replace serverDescription with a default ServerDescription of type "Unknown" | ||
# replace serverDescription with a default ServerDescription of type "Unknown" and an | ||
# error field describing that that primary was stale | ||
|
||
checkIfHasPrimary() | ||
return | ||
|
||
|
@@ -905,7 +909,8 @@ else: | |
for each server in topologyDescription.servers: | ||
if server.address != serverDescription.address: | ||
if server.type is RSPrimary: | ||
# See note below about invalidating an old primary. | ||
# See note below about invalidating an old primary and an error field describing that | ||
# the primary was stale | ||
replace the server with a default ServerDescription of type "Unknown" | ||
|
||
for each address in serverDescription's "hosts", "passives", and "arbiters": | ||
|
@@ -921,9 +926,11 @@ checkIfHasPrimary() | |
``` | ||
|
||
A note on invalidating the old primary: when a new primary is discovered, the client finds the previous primary (there | ||
should be none or one) and replaces its description with a default ServerDescription of type "Unknown." A multi-threaded | ||
client MUST [request an immediate check](server-monitoring.md#requesting-an-immediate-check) for that server as soon as | ||
possible. | ||
should be none or one) and replaces its description with a default ServerDescription of type "Unknown". Additionally, | ||
the `error` field of the new `ServerDescription` object MUST include a descriptive error explaining that it was | ||
invalidated because the primary was determined to be stale. Drivers MAY additionally specify whether this was due to an | ||
electionId or setVersion mismatch. A multi-threaded client MUST | ||
|
||
[request an immediate check](server-monitoring.md#requesting-an-immediate-check) for that server as soon as possible. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should we expand the scope of this ticket to include more info in other cases where we reset a server to "unknown" besides stale primary? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yeah I think that makes sense to do here. Seems like the only other place we do that is in the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. So there are two places we do this in our |
||
|
||
If the old primary server version is 4.0 or earlier, the client MUST clear its connection pool for the old primary, too: | ||
the connections are all bad because the old primary has closed its sockets. If the old primary server version is 4.2 or | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/tests/rs/new_primary.yml | ||
https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/tests/rs/primary_disconnect_setversion.yml | ||
https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/tests/rs/set_version_can_rollback.yml | ||
https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/tests/rs/setversion_equal_max_without_electionid.yml | ||
https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/tests/rs/setversion_greaterthan_max_without_electionid.yml | ||
https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/tests/rs/setversion_without_electionid-pre-6.0.yml | ||
https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/tests/rs/setversion_without_electionid.yml | ||
https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/tests/rs/stepdown_change_set_name.yml | ||
https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/tests/rs/use_setversion_without_electionid-pre-6.0.yml | ||
https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/tests/rs/use_setversion_without_electionid.yml |
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.
This paragraph is "a note on invalidating the old primary" so I don't think it applies to all the "electionId/setVersion mismatch" case and this sentence should be moved:
It should be moved to the paragraph below that starts with "If the server is primary with an obsolete electionId or setVersion,"