-
Notifications
You must be signed in to change notification settings - Fork 43
DOCSP-30349: server selection errors #548
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
Merged
rustagir
merged 6 commits into
mongodb:master
from
rustagir:DOCSP-30349-server-sel-errors
Jun 3, 2024
Merged
Changes from 2 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -204,6 +204,43 @@ Consider setting ``maxConnectionLifeTime`` and | |||||
maintains a connection to a MongoDB instance. For more information about these | ||||||
parameters, see :ref:`Connection Pool Settings <mcs-connectionpool-settings>`. | ||||||
|
||||||
.. _java-server-selection-errors: | ||||||
|
||||||
Server Selection Errors | ||||||
----------------------- | ||||||
|
||||||
MongoDB might not be able to complete a request even when some servers | ||||||
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.
Suggested change
|
||||||
are available, causing the driver to return a server selection error. | ||||||
The following list describes some situations in which you | ||||||
might encounter a server selection error: | ||||||
|
||||||
- You use tag sets in a read preference specification when no server | ||||||
jyemin marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
with those tags exists. | ||||||
- You write to a replica set when the primary node is unavailable. | ||||||
|
||||||
This error is of type ``MongoTimeoutException``. The following code | ||||||
jyemin marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
shows a sample of the exception that occurs if you attempt to send a | ||||||
request to a replica set without a primary: | ||||||
jyemin marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
|
||||||
.. code-block:: none | ||||||
|
||||||
com.mongodb.MongoTimeoutException: Timed out after 30000 ms while | ||||||
jyemin marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
waiting for a server that matches ReadPreferenceServerSelector{readPreference=primary}. | ||||||
|
||||||
Client view of cluster state is {type=REPLICA_SET, servers=[ | ||||||
{address=node01:27017, type=UNKNOWN, state=DISCONNECTED}, | ||||||
{address=node02:27017, type=REPLICA_SET_SECONDARY, roundTripTime=..., state=CONNECTED}, | ||||||
{address=node03:27017, type=REPLICA_SET_SECONDARY, roundTripTime=..., state=CONNECTED} | ||||||
]; | ||||||
|
||||||
The error includes a view of the cluster state that describes the | ||||||
connection state of each node. In the preceding error, the only | ||||||
connected servers are secondary nodes, ``node02`` and ``node03``. Thus, | ||||||
the request times out as MongoDB is unable to select a server that | ||||||
jyemin marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
satisfies the read preference of ``primary``. In this situation, reads | ||||||
jyemin marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||
can still be sent to the connected secondary nodes if you set the read | ||||||
preference to ``secondary``, ``secondaryPreferred``, or ``nearest``. | ||||||
|
||||||
.. _java-miscellaneous-errors: | ||||||
|
||||||
Miscellaneous Errors | ||||||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.